I just get server timeouts no matter what. So I assume you might be
working on your machine right now.
Regardless, your symptoms further enforce the server's "cookie parser"
as the cause in my puny brain.
After all, when you hit www.details.at for the /very first time/, your
browser is not sending the contents of the cookie in the header (because
it does not have the cookie yet), but when you make any subsequent
request - your browser IS sending the cookie in the header.
Furthermore, because cookie policy can be enforced by domain as well as
/individual host/, I think the addition of the later may actually expose
the section of Jetty code where the bug resides. Either that or the
contents of the cookie itself is a whole four characters longer ("www.")
thus exceeding the limit - a real stretch I admit.
I rest my feeble case.
Alan K. Holden
--~--~---------~--~----~------------~-------~--~----~
Open BlueDragon Public Mailing List
http://groups.google.com/group/openbd?hl=en
official site @ http://www.openbluedragon.org/
!! save a network - trim replies before posting !!
-~----------~----~----~----~------~----~------~--~---
