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

Switch middleware to avoid cookie packing, and use case mangling instead #636

Merged
merged 1 commit into from Feb 1, 2017
Merged

Conversation

bbangert
Copy link
Collaborator

Description

By mangling the case of the 'Set-Cookie' header, API Gateway will retain them all and include them as 'set-cookie' headers. This replaces the cookie packing which had issues with strict cookie parsers.

@coveralls
Copy link

coveralls commented Jan 30, 2017

Coverage Status

Coverage decreased (-1.2%) to 79.974% when pulling 67792f6 on bbangert:master into c99f4b2 on Miserlou:master.

@Miserlou
Copy link
Owner

Extremely excited about this feature! Out with the old hacks, in with the new ones.

Any chance you can repeal and replace the tests for this? Should actually increase overall coverage. It'd be great if you could also throw in some docstrings to the functions explaining what's happening here, and refer back to that pretty code you found on SO for proper attribution as well. 😸

@michi88
Copy link
Contributor

michi88 commented Jan 31, 2017

I can confirm that it's working. Getting multiple 'set-cookie' headers back. Whohoo!

@michi88
Copy link
Contributor

michi88 commented Jan 31, 2017

BTW, used a django app to test this.

@guyschlider
Copy link

Just tested it with my django project, works perfectly :D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants