On Tue, 6 Jul 1999, James Duncan Davidson wrote:
> > Yes, the JSDK Cookie.java code does have a version parameter, and by
> > default it is 0. The problem is that the Cookie constructor behaves
> > the same regardless of the value of the version parameter. In
> > particular, it checks that the cookie name is a valid HTTP 1.1 token,
> > a requirement *only* of version 1 cookies (per RFC 2109), not version
> > 0 cookies. (I mentioned this way back when they were taking comments
> > on the draft JSDK 2.0 spec, but I don't think it's yet been addressed
> > -- James Duncan Davidson, are you listening? :-)
>
> I'm always listening :)
>
> The latest javax.servlet.* classes in the JSDK 2.1 final and the WDK
> early access releases did have a modification to the Cookie.java source
> to relax some of the parsing issues (wrt bouncing out tokens).
[ ... ]
That's great to hear, thanks!
(Maybe someday soon I can stop using the hacked up Cookie.class file
I've been using :-).
Milt Epstein
Research Programmer
Software/Systems Development Group
Computing and Communications Services Office (CCSO)
University of Illinois at Urbana-Champaign (UIUC)
[EMAIL PROTECTED]
___________________________________________________________________________
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
