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

Do not encode already encoded url parameters when redirecting. #76

Merged
merged 1 commit into from
Jul 18, 2014
Merged

Do not encode already encoded url parameters when redirecting. #76

merged 1 commit into from
Jul 18, 2014

Conversation

oveddan
Copy link
Contributor

@oveddan oveddan commented Jul 18, 2014

This reverts commit c39a72b.

That commit was intended to stop rack ssl enforcer from erroring when it got a badly formed url, but it caused already encoded uri parameters to be encoded again.

This fixes #75, and also adds a test to verify that the parameters do not get double encoded.

…ical URIs"

This reverts commit c39a72b.

That commit was intended to stop rack ssl enforcer from erroring when it got a badly formed url, but it caused already encoded uri parameters to be encoded again.

It fixes #75, and also adds a test to verify that the parameters do not get double encoded.
tobmatth added a commit that referenced this pull request Jul 18, 2014
…-bug

Do not encode already encoded url parameters when redirecting.
@tobmatth tobmatth merged commit 08c555b into tobmatth:master Jul 18, 2014
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.

Already encoded url parameters get encoded again when redirecting
2 participants