Milt Epstein wrote:
> [snipped lots of good stuff about what's valid and not]
>
> Getting back to the original poster's problem, it was that there was
> an '=' in the cookie value. I missed that earlier, but it explains
> why no IllegalArgumentException's are thrown -- that only happens when
> the problem is with the name. I don't know where it was failing
> because of the '=' in the value, but it looks like it was failing
> somewhere (maybe it's in the servlet engine code and not the
> Cookie.java code).
I'm pretty sure the original problem was that if one incoming cookie has
an equal sign in the value, the servlet engine stops processing other
cookies (for instance the session ID cookie causing the session tracking
to fail). This was discussed at length about a year ago and I believe
most commercial servlet engines are corrected at this point (I know our
WAICoolRunner is), but apparently the web server in the JSDK is not.
It's in the engine code so it's hard (impossible?) to work around in
a servlet.
--
Hans Bergsten [EMAIL PROTECTED]
Gefion Software http://www.gefionsoftware.com
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
