we have to websites both https:// our customer can access one without issue,
the other one they have to add the website name in their proxy exception list
in their IE settings. Is there any settings in IIS on the actual website I
could update or look at? all firewall rules appear to be fine. Using IIS 6.0
running on a windows 2003 sp2 server. Thanks
On Nov 13, 3:32 pm, narnold33
wrote:
> we have to websites both https:// our customer can access one without issue,
> the other one they have to add the website name in their proxy exception list
> in their IE settings. Is there any settings in IIS on the actual website I
> could update or look at? all firewall rules appear to be fine. Using IIS 6.0
> running on a windows 2003 sp2 server. Thanks
Nothing to look at from IIS / server perspective. What you are talking
about is all client-side behavior.
For example, some browsers treat FQDN and names with "dots" in it
differently than names without "dots". IIS setting cannot affect
client behavior, other than if you change the hostname of the service.
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//
Hi,
No, there is nothing in IIS you can change. The problem is on the client
side, otherwise a client-side setting like this would not solve the problem.
--
Regards,
Kristofer Gafvert
http://www.gafvert.info/iis/ - IIS Related Info
narnold33 wrote:
>we have to websites both https:// our customer can access one without
>issue,
>the other one they have to add the website name in their proxy exception
>list
>in their IE settings. Is there any settings in IIS on the actual website I
>could update or look at? all firewall rules appear to be fine. Using IIS
>6.0
>running on a windows 2003 sp2 server. Thanks