-
Notifications
You must be signed in to change notification settings - Fork 330
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Adjust Punycode overflow checks * The change made in 1.0.0 incorrectly assumed that the input length limit removed the need to do overflow check when decoding. Now the internal-caller length limit is taken as a permission to skip overflow checks only when encoding. * The RFC gives overflow checking pre-flight math for languages like that don't have checked math. Since Rust does, the code now uses checked_add and checked_mul instead of pre-flight when overflow checks are performed. * Remove no_std category (crates.io doesn't support it, and it is now rejected), use keywords instead * Add benches that use the main idna 1.0 entry point in idna and url * Put the Unicode back end behind an adapter crate * Split fastest ASCII fast path from the rest * Bench hyphen in a domain that is otherwise lower-case ASCII * Adjust MSRV * Add README remarks about alternative Unicode back ends * Change the idna_adapter dependency to crates.io * Address clippy lints * Increment version number of idna to 1.0.3 * Test MSRV with idna unicode-rs back end and test ICU4X back end with 1.67 * Prepare url crate for publication with idna 1.0.3 (#987) --------- Co-authored-by: Manish Goregaokar <manishsmail@gmail.com> Co-authored-by: Valentin Gosu <1454649+valenting@users.noreply.github.com>
- Loading branch information
1 parent
08a3268
commit 8a683ff
Showing
22 changed files
with
8,539 additions
and
30,453 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,42 @@ | ||
# `idna` | ||
|
||
IDNA library for Rust implementing [UTS 46: Unicode IDNA Compatibility Processing](https://www.unicode.org/reports/tr46/) as parametrized by the [WHATWG URL Standard](https://url.spec.whatwg.org/#idna). | ||
|
||
## What it does | ||
|
||
* An implementation of UTS 46 is provided, with configurable ASCII deny list (e.g. STD3 or WHATWG rules). | ||
* A callback mechanism is provided for pluggable logic for deciding if a label is deemed potentially too misleading to render as Unicode in a user interface. | ||
* Errors are marked as U+FFFD REPLACEMENT CHARACTERs in Unicode output so that locations of errors may be illustrated to the user. | ||
|
||
## What it does not do | ||
|
||
* There is no default/sample policy provided for the callback mechanism mentioned above. | ||
* Only UTS 46 is implemented: There is no API to request strictly IDNA 2008 only or strictly IDNA 2003 only. | ||
* There is no API for categorizing errors beyond there being an error. | ||
* Checks that are configurable in UTS 46 but that the WHATWG URL Standard always set a particular way (regardless of the _beStrict_ flag in the URL Standard) cannot be configured (with the exception of the old deprecated API supporting transitional processing). | ||
|
||
## Usage | ||
|
||
Apps that need to prepare a hostname for usage in protocols are likely to only need the top-level function `domain_to_ascii_cow` with `AsciiDenyList::URL` as the second argument. Note that this rejects IPv6 addresses, so before this, you need to check if the first byte of the input is `b'['` and, if it is, treat the input as an IPv6 address instead. | ||
|
||
Apps that need to display host names to the user should use `uts46::Uts46::to_user_interface`. The _ToUnicode_ operation is rarely appropriate for direct application usage. | ||
|
||
## Cargo features | ||
|
||
* `alloc` - For future proofing. Currently always required. Currently, the crate internal may allocate heap but for typical inputs do not allocate on the heap (apart from the output `String` when applicable). | ||
* `compiled_data` - For future proofing. Currently always required. (Passed through to ICU4X.) | ||
* `std` - Adds `impl std::error::Error for Errors {}` (and implies `alloc`). | ||
* By default, all of the above are enabled. | ||
|
||
## Alternative Unicode back ends | ||
|
||
By default, `idna` uses [ICU4X](https://github.com/unicode-org/icu4x/) as its Unicode back end. If you wish to opt for different tradeoffs between correctness, run-time performance, binary size, compile time, and MSRV, please see the [README of the latest version of the `idna_adapter` crate](https://docs.rs/crate/idna_adapter/latest) for how to opt into a different Unicode back end. | ||
|
||
## Breaking changes since 0.5.0 | ||
|
||
* Stricter IDNA 2008 restrictions are no longer supported. Attempting to enable them panics immediately. UTS 46 allows all the names that IDNA 2008 allows, and when transitional processing is disabled, they resolve the same way. There are additional names that IDNA 2008 disallows but UTS 46 maps to names that IDNA 2008 allows (notably, input is mapped to fold-case output). UTS 46 also allows symbols that were allowed in IDNA 2003 as well as newer symbols that are allowed according to the same principle. (Earlier versions of this crate allowed rejecting such symbols. Rejecting characters that UTS 46 maps to IDNA 2008-permitted characters wasn't supported in earlier versions, either.) | ||
* `domain_to_ascii_strict` now performs the _CheckHyphens_ check (matching previous documentation). | ||
* The ContextJ rules are now implemented and always enabled, even when using the old deprecated API, so input that fails those rules is rejected. | ||
* The `Idna::to_ascii_inner` method has been removed. It didn't make sense as a public method, since callers were unable to figure out if there were errors. (A GitHub search found no callers for this method.) | ||
* Punycode labels whose decoding does not yield any non-ASCII characters are now treated as being in error. | ||
* When turning off default cargo features, the cargo feature `compiled_data` needs to be explicitly enabled. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.