W3C home > Mailing lists > Public > www-jigsaw@w3.org > March to April 2007

RE: Cookie parsing issue...

From: Laird, Brian <BLaird@havigs.com>
Date: Tue, 20 Mar 2007 10:31:42 -0500
Message-ID: <198C7B6593B76E44B30C3AAC456E57A1027B1691@electra.Perseco.com>
To: "Yves Lafon" <ylafon@w3.org>
Cc: <www-jigsaw@w3.org>, "Mrozinski, Ken" <KMrozinski@havigs.com>

Hey Yves,

Your fix worked perfectly plus it makes a lot more sense then some of the other things we were trying.  I not too sure where you are on doing a 2.2.6 release, but do you think you can integrate this fix and push out a minor release (ex: 2.2.5b)?  

Thanks again for the help,
Brian

-----Original Message-----
From: Yves Lafon [mailto:ylafon@w3.org] 
Sent: Tuesday, March 20, 2007 9:03 AM
To: Laird, Brian
Cc: www-jigsaw@w3.org; Mrozinski, Ken
Subject: RE: Cookie parsing issue...

On Tue, 20 Mar 2007, Laird, Brian wrote:

> Hey Yves,
>
> Well I spent some time trying to implement your fix and here is what I 
> found:
>
> The problem actually exists in the HttpParser.  What I think is 
> happening is that the third call to the parser (from the HttpCookieList 
> class) to get the value of the cookie is stopping on the equals sign 
> because that is the delimiter.
>
> I think this is easier to explain via an example.  Below is an example 
> cookie header.
>
> Cookie: HGS$$LocaleCookie=en_US; CHALLENGE_COOKIE=Y3hBsq1lr9AxMTE2; 
> CARDTYPE=card
>
> The first call to the parse routine using the cv (ParseState) yields the 
> following: CHALLENGE_COOKIE=Y3hBsq1lr9AxMTE2==
>
> This is correct.  The next call to the parse routine using the it 
> variable (ParseState) yields the following which is the name of cookie. 
> Now the it variable was initialized with the equals sign as the 
> separator.
>
> CHALLENGE_COOKIE
>
> The third call to the parse routine is where we lose the equals sign. 
> The routine returns the following:
>
> Y3hBsq1lr9AxMTE2
>
> In the HttpParser, as it runs through the bytes it is checking to see if 
> it hit the separator.  Once it does find the separator it assumes it is 
> complete.
>
> Now I looked to see how to fix this and I am kind of at a loss.  Here is 
> what we did try to do:
>
> - Tried implementing your fix but that resulted in an infinite loop.  I 
> think that has to do with how the ParseState is keeping track of the 
> position in the raw bytes and then where the separator shows up.

Yes, I know why now, the test should have been >= 0 instead of < 0. But 
see below:

> - Create a new ParseState object with a separator that would never be 
> found in a cookie.  Unfortunately, we could never get it work correctly. 
> I don't think we set the start & end variables correctly.
>
> - Change the existing it variables separator to something that would 
> never be found in a cookie.  Again that didn't work right.
>
> - We looked at just rewriting the whole parse routine but we were afraid 
> that we will introduce some bugs that you have long since resolved due 
> to browser compatibility type stuff.

That would be ideal for this special case, but another way would be to 
tweak the ParseState to go directly to the end of the buffer before 
calling it.toString(raw);
In that case, as we know the end of the buffer (above you can read 
it.bufend = cv.end;)
So the "right" fix is to do:
             } else {
 		c.setValue(it.toString(raw));
 	    }
=>
             } else {
                 // we know that we must read everything from the first
                 // separator (in case there are multiple instances)
 	        it.end = cv.end;
                 c.setValue(it.toString(raw));
             }

> We are perfectly willing to do the work if you could just provide some 
> direction as to how best to resolve this issue.

The HTTP parser has been optimized to reduce copying while parsing, that's 
why it may be a bit hairy in some cases, but that's the cost of trying to 
be efficient
Cheers,

-- 
Baroula que barouleras, au tiéu toujou t'entourneras.

         ~~Yves


************************************************************************
This e-mail and any accompanying documents or files contain information that is the 
property of HAVI Global Solutions, that is intended solely for those to whom this e-mail is addressed 
(i.e., those identified in the "To" and "Cc" boxes), and that is confidential, proprietary, 
and/or privileged.  If you are not an intended recipient of this e-mail, you are hereby 
notified that any viewing, use, disclosure, forwarding, copying, or distribution of any of 
this information is strictly prohibited and may be subject to legal sanctions.  If you have 
received this e-mail in error, please notify the sender immediately of any unintended 
recipients, and delete the e-mail, all attachments, and all copies of both from your system.

While we have taken reasonable precautions to ensure that any attachments to this e-mail 
have been swept for viruses, we cannot accept liability for any damage sustained as a 
result of software viruses.
************************************************************************

Received on Tuesday, 20 March 2007 15:29:43 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 9 April 2012 12:13:38 GMT