RE: Cookie parsing issue...

THANKS, YVES!  I WILL TRY THAT TODAY TO SEE IF THAT FIXES
THE PROBLEM.

BRIAN

-----ORIGINAL MESSAGE-----
FROM: "YVES LAFON" <YLAFONW3.ORG>
TO: "LAIRD, BRIAN" <BLAIRDHAVIGS.COM>
CC: "WWW-JIGSAWW3.ORG" <WWW-JIGSAWW3.ORG>
SENT: 3/16/2007 7:51 AM
SUBJECT: RE: COOKIE PARSING ISSUE...

ON FRI, 16 MAR 2007, YVES LAFON WROTE:

>
> ON FRI, 16 MAR 2007, LAIRD, BRIAN WROTE:
>
>> I HOPE THINGS ARE WELL; IT HAS BEEN A WHILE SINCE
WE HAVE TALKED.  WE
>> CAME ACROSS A PROBLEM I AM HOPING YOU (OR SOMEONE
WHO KNOWS THE JIGSAW
>> CODE WELL) CAN HELP US WITH.  IN A MAJORITY OF OUR
PROCESSING WE ARE
>> USING SOME RANDOMLY GENERATED COOKIE VALUES FROM A
THIRD PARTY AS KIND
>> OF A SESSION IDENTIFIER.  WELL A FEW DAYS AGO THE
VALUE BEING GENERATED
>> STARTED TO LOOK LIKE THIS (WITHOUT THE DOUBLE
QUOTES):
>> "0_0RBEAWFLUXOTIXNJGYMDMZMW==".  WE ALSO
STORE THIS VALUE IN MEMORY AND
>> COMPARE IT TO THE COOKIE WHEN THE USER COMES BACK
TO OUR SITE.

OK, I LOCATED THE ISSUE, THE PARSING IS DONE IN 
ORG.W3C.WWW.HTTP.HTTPCOOKIELIST, IN PARSE(), THE PARSER HAS
'=' AS A 
SEPARATOR, HENCE THE ISSUE YOU SEE.

YOU CAN TRY TO CHANGE
     C.SETVALUE(IT.TOSTRING(RAW));

BY

STRINGBUFFER SB = NEW STRINGBUFFER(IT.TOSTRING(RAW));
WHILE (HTTPPARSER.NEXTITEM(RAW, IT) < 0 ) {
     SB.APPEND('=');
     SB.APPEND(IT.TOSTRING(RAW);
}
C.SETVALUE(SB.TOSTRING());

AND SEE IF THAT FIXES THE ISSUE.

-- 
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.
************************************************************
************