urlnorm is breaking a legitimate use of two successive slashes in our URLs.
Here is an example of what is happening:
http://example.com/login?redirect-back-to=http://example.com/homepage
urlnorm'd is http://example.com/login?redirect-back-to=http:/example.com/homepage
@jehiah would you be open to adding a special case to not collapse two successive slashes that follow http: or https:? I am willing to put in a pull request for this but I wanted to check if it would be accepted first.
Ideally urlnorm would support all of the official URI schemas, not just http and https but since the list is large I think just checking http and https would satisfy 90% of people.
urlnorm is breaking a legitimate use of two successive slashes in our URLs.
Here is an example of what is happening:
http://example.com/login?redirect-back-to=http://example.com/homepageurlnorm'd is
http://example.com/login?redirect-back-to=http:/example.com/homepage@jehiah would you be open to adding a special case to not collapse two successive slashes that follow
http:orhttps:? I am willing to put in a pull request for this but I wanted to check if it would be accepted first.Ideally urlnorm would support all of the official URI schemas, not just http and https but since the list is large I think just checking http and https would satisfy 90% of people.