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
We are using furl to normalize templated URLs:
furl
normalized_url = furl(rendered_url).tostr("&", False)
But we encounter a bit of an odd behavior when normalizing URLs which have a very specific fragment, and aren't sure if this is an expected or not.
For example normalizing following URL yields an unexpected result (fragment's forward slash gets percent-encoded):
normalized_url = furl("https://example.com/path/#/foo=123").tostr("&", False) # Actual: https://example.com/path/#%2Ffoo=123 # Expected: https://example.com/path/#/foo=123
However when the URL fragment contains a separator (?) or does not contain an equals sign (=) it works as expected:
?
=
normalized_url = furl("https://example.com/path/#/?foo=123").tostr("&", False) # Actual: https://example.com/path/#/?foo=123 # Expected: https://example.com/path/#/?foo=123 normalized_url = furl("https://example.com/path/#/foo").tostr("&", False) # Actual: https://example.com/path/#/foo # Expected: https://example.com/path/#/foo
We are using the latest version of furl==2.1.2.
furl==2.1.2
Looking forward to your feedback.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
We are using
furl
to normalize templated URLs:But we encounter a bit of an odd behavior when normalizing URLs which have a very specific fragment, and aren't sure if this is an expected or not.
For example normalizing following URL yields an unexpected result (fragment's forward slash gets percent-encoded):
However when the URL fragment contains a separator (
?
) or does not contain an equals sign (=
) it works as expected:We are using the latest version of
furl==2.1.2
.Looking forward to your feedback.
The text was updated successfully, but these errors were encountered: