percent_encoding: normalise_percent_encoded and strict_percent_encoded
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.6k
- Forks
- 406
- PR merge metrics
- No merged PRs in 30d
Description
As part of an unrelated WebDAV specific project, I've written two utility functions closely tied to percent encoding:
- normalise_percent_encoded(): Decodes percent-encoded strings while keeping RFC 3986 reserved characters encoded (with uppercase normalization).
- strict_percent_encoded(): Encodes non-reserved characters for safe URI paths.
These are actually not webdav-specific at all, and re-usable in other HTTP-related contexts.
Do you consider these a suitable contribution for the percent_encoding crate? If so, I can draft a PR incorporating both of these. The implementation for these is quite non-trivial, and they have been heavily optimised to minimise allocations and heavily tested.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked docs.rs entries for normalise_percent_encoded() and strict_percent_encoded(), then compare their HTTP and URI-path use cases with the percent_encoding crate. The contribution is complete when maintainers confirm both utilities belong in the crate and an accepted PR incorporates the implementations with their existing optimization and test coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100