Getting started

The crate declares Rust 1.96.0 as its compiler compatibility baseline. Default features provide the complete documented extraction API.

With all common API families enabled:

[dependencies]
http-extract = "0.1"

For a smaller dependency surface, disable defaults and enable only the features you use:

[dependencies]
http-extract = { version = "0.1", default-features = false, features = [
  "authority",
  "content-type",
] }

Header functions contain the parsing logic. Request functions are convenience wrappers that only delegate through request.headers():

#![allow(unused)]
fn main() {
use http_extract::{Request, extract_request_authority, extract_request_content_type};

let request = Request::builder()
    .uri("https://example.com/items")
    .header("content-type", "application/json")
    .body(())?;

assert_eq!(
    extract_request_authority(&request)?.unwrap().as_str(),
    "example.com"
);
assert_eq!(
    extract_request_content_type(&request)?.unwrap().essence_str(),
    "application/json",
);
Ok::<(), Box<dyn std::error::Error>>(())
}

A socket peer is not an HTTP field. Obtain it from the server adapter. If the adapter stores a SocketAddr directly in request extensions, use extract_request_socket_address or extract_request_socket_ip. With the non-default axum feature, extract_axum_socket_address reads an existing ConnectInfo<SocketAddr> request extension, while extract_axum_socket_ip returns its IP component; neither fabricates that fact. extract_socket_ip composes the Axum and direct extension sources without reading Headers.

The Header-based extract_client_ip convenience does not use or authenticate the transport peer, so its result remains untrusted. For an explicitly trusted-proxy deployment, extract_proxy_client_ip checks the default Header order and falls back to extract_socket_ip only when all Headers in CLIENT_IP_HEADERS are absent. It does not verify the proxy trust boundary.

Before deployment, review Standards and compatibility, Features, and the client IP trust boundary.