Skip to content
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

Checks if cookies is empty before adding to header #3150

Merged
merged 2 commits into from
Aug 14, 2016
Merged

Checks if cookies is empty before adding to header #3150

merged 2 commits into from
Aug 14, 2016

Conversation

TheLonelyGhost
Copy link
Contributor

@TheLonelyGhost TheLonelyGhost commented Aug 13, 2016

see greyblake/crystal-cossack#4

One item that is unclear is if it should erase the previous cookies if there are none in the instance of HTTP::Cookies.

I erred on the side of erasing them still, since I assume the canonical representation of the cookies is more likely to be the instance of HTTP::Cookies.

@jhass
Copy link
Member

jhass commented Aug 13, 2016

Could you try to write a spec for this? :)

@TheLonelyGhost
Copy link
Contributor Author

Oops! Forgot to include it in this branch. See latest update for specs.

@jhass jhass merged commit 7ac9a53 into crystal-lang:master Aug 14, 2016
@jhass
Copy link
Member

jhass commented Aug 14, 2016

Thank you!

@TheLonelyGhost TheLonelyGhost deleted the empty-cookies-should-not-set-cookie-header branch August 15, 2016 01:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants