-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixed cookies parsing #133
Conversation
afanasy
commented
Dec 12, 2011
- correct handling of cookies values with equal sign (sid="c2lkDQo=")
- improved default path parsing
- updated tests
i'd like some eyes on this who've been in this code, I haven't spent enough time in in it. |
I've added comments |
Hi. I'm not sure if this is related but the new version of request does not appear to handle cookies correctly. Or rather, not as well as it used to. After spending a morning trying to work out why some previously working code had stopped functioning I narrowed it down to the header information sent and saw that the cookie I was sending appeared to be undefined. I am now using an old version of request (not sure which version it is but I installed it 18/11/2011) and that works correctly.
|
latest release or master? |
So what's up with this request? Its kind of fixes a major bug. |
The latest release (the version one gets with "npm install request"). The weird thing is I tested this version with a simple php file that reads header data and all appeared fine, including cookies. It's just that the response coming back for the code mentioned above indicates that I am send an "undefined" sessionid (a cookie) but with the older version of request the response shows the correct sessionid sent. |
pushed new version with this fix in it. |
great, thanks! |