More information:
Looks like this is not related the the secure nature (digitally signed)
of the cookie, but the size. A cookie over about 3k will trigger this
problem.
Also, it looks like Tomcat doesn't receive the request, so the problem
may be in SSL. It is hard to tell, since it seems
Leonard Sitongia wrote:
More information:
Looks like this is not related the the secure nature (digitally signed)
of the cookie, but the size. A cookie over about 3k will trigger this
problem.
Also, it looks like Tomcat doesn't receive the request, so the problem
may be in SSL. It is hard to
On Jan 6, 2005, at 11:03 AM, Leonard Sitongia wrote:
Looks like this is not related the the secure nature (digitally
signed) of the cookie, but the size. A cookie over about 3k will
trigger this problem.
Resolved this by increasing the bufferSize and maxHttpHeaderSize in the
Tomcat
On Jan 6, 2005, at 12:07 PM, Wade Chandler wrote:
I don't know the answer...figured I would try to give you help in
thinking about the issue.
Thanks! That was just the kind of thinking I was hoping to hear. If
not an answer, then it sure helps to get ideas of other ways of
experimenting.
I have configured Tomcat 5.0.27 on the localhost to accept https
connections (I have configured an unsigned cert under the alias
tomcat to allow this).
I can then get to the root Tomcat page at https://localhost:8443/.
If my browser happens to have a signed cookie in it (this cookie is a
