It's not supposed to, but then I haven't used 3.2.x for a very long time.
The first thing that I would try is to upgrade my isapi_redirect.dll from
http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1.2.2
/bin/win32/. It should be fully compatible with the 3.2.x Java code.
Varley, Roger [EMAIL PROTECTED] wrote in message
0D309F7200E8D611AB870002B335ADACA92D38@EXHUB01">news:0D309F7200E8D611AB870002B335ADACA92D38@EXHUB01...
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
