Has anyone run into this:
There is an IIS5 WWW server behind the ASL. Users authenticating to the IIS web application either do not get prompted for a username/password, or they end up seeing someone else's cached information.
HTTP proxy is disabled.
I am believeing it is a problem with the programming on the IIS machine, but the developers think it is the firewall. I do not see how this could be possible when all the ASL is doing is filtering packets. There should be no caching of any kind going on.
This thread was automatically locked due to age.