Enum ParseError 

pub enum ParseError {
    Empty,
    InvalidComponent(Component),
    ControlCharInUri {
        at: usize,
        byte: u8,
    },
    InvalidPercentEncoding {
        at: usize,
    },
    IPv6ZoneNotSupported,
    StrictViolation,
    TooLong {
        len: usize,
    },
    NonUtf8 {
        at: usize,
    },
}

Available on crate feature net only.

Reasons parsing a byte string into a Uri can fail.

Graceful by default: the regular Uri::parse entry point (lands in M3) accepts inputs that browsers and curl tolerate. Only inputs in the “differential-parse hazard” set (control chars, backslash-as-slash, alternate IPv4 forms, etc.) are unconditionally rejected — and those are the variants below that can fire even from parse.

Uri::parse_strict (lands in M3) additionally rejects everything outside RFC 3986 with ParseError::StrictViolation.

Variants

Empty

The input was empty.

InvalidComponent(Component)

A URI component is structurally invalid: bad delimiter placement, disallowed character, empty where forbidden, etc. The wrapped Component identifies which one. More specific failure modes (control chars, percent-encoding, etc.) have their own variants below.

ControlCharInUri

A \0, \r, \n, \t, or other ASCII control character was found inside a URI component. Always rejected — these are header-injection and request-smuggling vectors.

Fields

at: usize

byte: u8

InvalidPercentEncoding

A percent-encoded escape was malformed — % not followed by two hex digits, or (after decoding) the resulting byte is itself disallowed in the component where it appeared.

Fields

at: usize

IPv6ZoneNotSupported

An IPv6 literal carried a zone identifier (%25en0 on the wire). Not currently supported — see module-level docs for the path forward.

StrictViolation

Strict-mode-only rejection: input parsed under graceful rules but violates RFC 3986. Only produced by Uri::parse_strict (M3).

TooLong

The URI exceeded the maximum representable length.

Fields

len: usize

NonUtf8

Input bytes were not valid UTF-8.

Graceful mode tolerates raw UTF-8 in path / query / fragment (browsers and curl do too), but the bytes must still be valid UTF-8 — every component accessor returns &str, and the presence of a stray continuation byte or truncated multi-byte sequence would otherwise be UB at access time.

Always rejected. Strict mode rejects more aggressively (per-byte ASCII grammar checks), but this is the floor.

Fields

at: usize

Trait Implementations

impl Clone for ParseError

fn clone(&self) -> ParseError

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for ParseError

fn fmt(&self, f: &mut Formatter<'_>) -> Result<(), Error>

Formats the value using the given formatter.

impl Display for ParseError

fn fmt(&self, f: &mut Formatter<'_>) -> Result<(), Error>

Formats the value using the given formatter.

impl Error for ParseError

fn source(&self) -> Option<&(dyn Error + 'static)>

Returns the lower-level source of this error, if any.

fn description(&self) -> &str

👎Deprecated since 1.42.0:

use the Display impl or to_string()

fn cause(&self) -> Option<&dyn Error>

👎Deprecated since 1.33.0:

replaced by Error::source, which can support downcasting

fn provide<'a>(&'a self, request: &mut Request<'a>)

🔬This is a nightly-only experimental API. (error_generic_member_access)

Provides type-based access to context intended for error reports.

impl PartialEq for ParseError

fn eq(&self, other: &ParseError) -> bool

Tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

Tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl Eq for ParseError

impl StructuralPartialEq for ParseError