This article was originally published in PC Pro and is reproduced with permission.
We recently had a problem with a Web site hosted on an IIS server, and that makes heavy use of session variables to track what the user's doing.
Users were reporting that the site wasn't behaving as expected; we eventually traced this to the user clicking on a certain link while using Netscape. How could the choice of browser affect session variables (stored on the server)? The answer was a difference in case sensitivity between IE and Netscape when specifying the server's virtual directory in the browser URL. If, for example, your site is called Fred, the URL to your root project might be http://servername/Fred/. Create a link to home.asp like this:
<a href="/Fred/html/home.asp">Goto Home Page</a>then you should have no problem getting session variables tracked properly between pages on your site. If, however, you write the link as:
<a href="/fred/html/home.asp">Goto Home Page</a>and Netscape creates a new session because of its case sensitivity, hence the session values seem to disappear. It's a mistake that's very easy to make, and incredibly difficult to find.
All articles Copyright CST Group Limited ©1997-2024
Let's Talk
Whether you have a new or existing project, we’d love to hear from you.
Our experienced team thrive on problem solving and working with your business goals in mind.