Module http 

HTTP client implementation.

Natively every request goes through reqwest (TLS, HTTP/2, a pooled client per host). In the browser build it goes through transport, hyper 1’s HTTP/1.1 client over the page’s virtual loopback — reqwest’s wasm backend is the browser’s fetch, which is not Send and cannot reach NetGet’s in-page servers. Everything above the round trip — the command channel, the model’s answers, the follow-up chain — is the same code on both.

Re-exports

pub use crate::client::http_fetch::transport;

pub use crate::client::http_fetch::transport::HttpExchange;

pub use actions::HttpClientProtocol;

Modules

actions

HTTP client protocol actions implementation

Structs

HttpClient

HTTP client that makes requests to remote HTTP servers