Hello,

I have a cluster of IIS 5.0 web servers with Cisco's Local Director (LD) load balancing software. Apparently, requests directed to the web servers through Local Director require a forward slash at the end of the URL ("/"), as this is apparently proper hypertext transfer protocol (HTTP).

I have an issue for a client where they have an application server with web services outputting XML back to the web server. This XML is then transformed to HTML by XSL. Currently, with the way the web server and LD are set up, if there is no forward slash at the end of the URL, the server recognizes this as a bad request and asks the client to resend the URL, and the response sent back to the client is "Page Not Displayed".

To clarify, they are not using the standard port 80 used for web traffic, rather they are using port 8040 for security reasons. Also, state information is stored on the database server.

Currently in the development environment, our workaround is to define port 8040 as a LD virtual port. Howeve, for production rollout, we would like to find another solution to this. My first thought was to go through our HTML and Javascript to include the forward slash. Our client says that whenever they develop web pages, they make sure that all references to URLs (ie hyperlinks) include the forward slash.

Has anyone else run into a situation like this? Any suggestions or input would be greatly appreciated

Regarsd
//Marko