We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When you already have encoded url parameters, and rack-ssl-enforcer performs a redirect, the parameters get encoded again.
So if you have a url such as: http://www.app.com/email?email=someemail%40somedomain.com It gets encoded and redirected to: https://www.app.com/email?email=someemail%254040somedomain.com
This is not desirable behavior.
This bug is caused by this commit: 1ef4515
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
When you already have encoded url parameters, and rack-ssl-enforcer performs a redirect, the parameters get encoded again.
So if you have a url such as:
http://www.app.com/email?email=someemail%40somedomain.com
It gets encoded and redirected to:
https://www.app.com/email?email=someemail%254040somedomain.com
This is not desirable behavior.
This bug is caused by this commit: 1ef4515
The text was updated successfully, but these errors were encountered: