hyper

yeah me too
sounds like a config problem to me

there are tons of reasons
such as this one



with a non-standard port, if you specify the trailing slash on a URL, IIS
leaves the URL alone. Leave the trailing slash off, and IIS does a
redirection to the URL with the trailing slash, and *adds the port number*
to the URL. This is an issue that comes up if you have a need to run sites
on different ports and have a piece of equipment in front masking the ports
to keep things nice looking:

http://all.your.org/are/belong/

This url points to port 80 (the assigned port), but when it reaches me, I've
got a LocalDirector that knows it really goes to all.your.org:4553. So it
sends the request on to my IIS server at port 4553 instead of 80. IIS is
okay with the URL like this (with the trailing slash) --nothing gets
transmuted. On the other hand,

http://all.your.org/are/belong

hits the LocalDirector just fine, and the LD pushes it to my IIS server's
port 4553, but IIS tweaks it with a redirect to

http://all.your.org:4553/are/belong/

which, for a couple reasons, can cause headaches and goose chasing.

Solution?

(1) don't omit the trailing slash on sites that are not on default ports (80
or 443)
(2) the LocalDirector needs to listen to the non-standard port for requests
in the event the URL does get changed to include the port number

__________________