Ok... Gotcha... So, the session _IS_ correctly handled if going thru
cookies, but if it's URLencoded, it's not...

Will dig into that tomorrow first thing in the morning (bear with me, can
you please post a bug in BugZilla so that we can keep track of what was
found faulty and when it was fixed, I know, it's a big pain in the ass,
but... :) :) :)

Should be an easy fix.... (unlikely bug #2933)

Eryq at [EMAIL PROTECTED] wrote:
> 
> Browser    Access    Cookies
> cookies    via    on in
> enabled    apache    Context    RESULT:
> ------    ------    ------    ------
> no    no    no    ok
> no    no    yes    ok
> no    yes    no    FAIL [1]
> no    yes    yes    FAIL [2]
> yes    no    no    ok
> yes    no    yes    ok
> yes     yes    no    FAIL [3]
> yes    yes    yes    ok
> 
> [1] 404 on the jsessionid=....
> [2] 404 on the jsessionid=....
> [3] Apache asks the browser for a cookie.

[3] happens because sessions are not get from the URL, so, Tomcat forces a
cookie request if cookies can be accepted by the browser...

Thanks _SO_MUCH_ for the invaluable input...

    Pier

Reply via email to