Crates.io | fqdn |
lib.rs | fqdn |
version | |
source | src |
created_at | 2021-09-22 09:12:11.873852 |
updated_at | 2024-11-18 10:06:17.169109 |
description | FQDN (Fully Qualified Domain Name) |
homepage | |
repository | https://github.com/Orange-OpenSource/fqdn |
max_upload_size | |
id | 454785 |
Cargo.toml error: | TOML parse error at line 18, column 1 | 18 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include` |
size | 0 |
Fully Qualified Domain Name
This crate allows basic manipulation of FQDN with an inner representation compatible with the RFC 1035.
So, all comparisons between character strings (e.g., labels, domain names, etc.) are done in a case-insensitive manner. Of course, FQDN hashing follows this behaviour. Note that FQDN are internally converted to lowercase.
Notice that this RFC introduces some size limits which are not
set by default in this crate.
The feature strict-rfc
activates all of them
but each of them could be activated independently of the others:
domain-label-length-limited-to-63
)domain-name-length-limited-to-255
)domain-name-without-special-chars
)domain-name-should-have-trailing-dot
): notice that activating this feature
modifies the behaviour of Display
which adds a period at the end of the FQDN.The only feature activated by default is the following:
domain-label-cannot-start-or-end-with-hyphen
)