Skip to content

URL Encoding Bugs when dealing with already encoded URLs #3449

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

Closed
tedivm opened this issue Jan 18, 2019 · 2 comments
Closed

URL Encoding Bugs when dealing with already encoded URLs #3449

tedivm opened this issue Jan 18, 2019 · 2 comments
Labels
bug something broken

Comments

@tedivm
Copy link

tedivm commented Jan 18, 2019

Plotly seems to be doing some weird things with character encoding that results in unexpected behavior.

Take the URL /projects/Project #1 as an example. The only way to use that character in a URL is to escape it, turning it into /projects/Project %231- or, if we're encoding everything, /projects/Project%20%231.

Unfortunately when presented with that URL Plotly decides to encode the center % sign (but only that one, it ignores the %20), turning it into /projects/Project%20%25231

This makes it impossible to actually use the # sign in URLs related to Plotly.

Codepen Example

Ideally there would be an option for Plotly to take the URL as is.

@etpinard
Copy link
Contributor

Thanks for the report!

@gvwilson
Copy link
Contributor

Hi - this issue has been sitting for a while, so as part of our effort to tidy up our public repositories I'm going to close it. If it's still a concern, we'd be grateful if you could open a new issue (with a short reproducible example if appropriate) so that we can add it to our stack. Cheers - @gvwilson

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

No branches or pull requests

3 participants