-
Notifications
You must be signed in to change notification settings - Fork 66
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
[DISC] Percent decoding #98
Comments
You probably want to file an issue at https://github.com/servo/rust-url/ and use the |
@erwanvivien wondering if you were able to come across a solution? Thanks to your hack I am able to get my current code working (i.e no invalid UTF8 error), but receiving raw bytes in URL params is proving to be a problem to otherwise decode currently... Current hack (inspired by yours: ckcr4lyf/kiryuu@2536307#diff-42cb6807ad74b3e201c5a7ca98b911c5fa08380e942be6e4ac5807f8377f87fcR29) |
Hello @ckcr4lyf, I'm still, to this day, using the said "hack"... Why is there no function to decode only the keys, not the values ?
Thanks |
I am not too sure myself, I wasn't really able to read the source that well... I will try and figure out if the % decoding is an issue at this library's usage of rust-url or it comes due to a higher level issue of auto decoding in rust-url |
@erwanvivien seems it is a design choice by the parent library to not support invalid UTF-8, as is mentioned in this spec which they follow - https://url.spec.whatwg.org/#urlencoded-parsing Guess no choice except the hack, thanks for sharing it! |
Hello everyone,
Could we have a feature where
from_str
returns values with no parsing ?Which yield
I'm using the above code for now to escape '%' character
Sorry if issue isn't the best suited place.
Thanks
Edit: added output
The text was updated successfully, but these errors were encountered: