DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=36457>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=36457 ------- Additional Comments From [EMAIL PROTECTED] 2005-09-01 14:31 ------- I found the reason for it. Both cookies are set without a path. HttpClient than takes the path of the request and stores the cookie with it. GET /on/demandware.store/WFS/Demos-YourShopHere-Site Set-Cookie: dwrequestid=9iJfAEMW1Cl7AwAK GET /on/demandware.store/WFS/Demos-YourShopHere-Site/en_US/-/USD/ViewSimpleSearch-Start Set-Cookie: dwrequestid=9iJlAEMW1DF7AwAK Therefore both cookies are different. When both cookies are stored with an non-empty path, why is the path not set at the next request to the server? Of course there is not path in the Set-Cookie, so there is not path to set, but why do we have two cookies than? I checked the RFC2109 and did not find any definition for an empty cookie path. Path is optional. So, what to do? My Firefox at least is thinking differently and overrides the cookie all the time. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
