Hello,
I will see what I can do, after I get a bit more familiar with the Tomcat
architecture.
It appears that this may involve modifications to the connectors. As a
quick fix for anyone that is interested, and if you are using mod_jk to
connect to Apache like myself, you can comment out the lin
"Raiden" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> Hello,
>
> Anyone have any ideas if there is a solution to this problem in 4.1.12, or
> are we better off reverting back to Tomcat 3.3.2 to restore the old
> behavior of not making the sessionId cookie a s
Hello,
Anyone have any ideas if there is a solution to this problem in 4.1.12, or
are we better off reverting back to Tomcat 3.3.2 to restore the old
behavior of not making the sessionId cookie a secure cookie if the session
was created under https?
Thanks in advance!
-Raiden
On Mon, 25 Nov 20
Hello,
Tomcat 3.3.2 has a secureCookie paramater that restores the old behavior
of not making the sessionId cookie a secure cookie if it was created
under https. Is there such a parameter in 4.1.12?
I know there has been a thread debating the reasons as to why a
session that is created under htt