I've done some more investigation. If I replace
'response.sendRedirect(response.encodeRedirectURL("../default.htm"))' with
'response.sendRedirect("../default.htm");' then everything works as
expected, so there is something about response.encodeRedirectURL() that I'm
not uderstanding. I've looked through the isapi.log and I've noticed that
when using
response.encodeRedirectURL() that the resulting call for the first call (and
the first call only) in a session is something like
/application/default.htm;jsessionid=0c1stutim1 - which is the correct path.
I was wondering, could IIS be considering the ';jsessionid=' string as being
part of the actual path to the page?Regards Roger -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
