Skip to content
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

Feature request: Provide customary RFC 3986 encoding #863

Open
1 task
daniel-pfeiffer opened this issue Aug 4, 2023 · 0 comments
Open
1 task

Feature request: Provide customary RFC 3986 encoding #863

daniel-pfeiffer opened this issue Aug 4, 2023 · 0 comments

Comments

@daniel-pfeiffer
Copy link

  • Note that this crate implements the URL Standard not RFC 1738 or RFC 3986

Note taken, but why? RFC 3986 (or even wider open) is the standard everybody follows for URLs. While Chrome and FF are represented in that WG, they do not follow this nonsense in their encodeURIComponent().

And it makes a huge difference for human readability! It would cost you nothing to add one with these 4 harmless characters:

const RESERVED/*_RFC_3986*/: &AsciiSet = &NON_ALPHANUMERIC
    .remove(b'-')
    .remove(b'.')
    .remove(b'_')
    .remove(b'~');

Or the other way round, adding to CONTROLS, and then NON_ALPHANUMERIC to this one.

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

No branches or pull requests

1 participant