pub struct Capabilities {Show 15 fields
pub streaming: bool,
pub upload_streaming: bool,
pub upload_progress: bool,
pub manual_redirects: bool,
pub auth_questions: bool,
pub native_auth_schemes: bool,
pub server_trust: bool,
pub client_identity: bool,
pub platform_cookies: bool,
pub platform_cache: bool,
pub metrics: bool,
pub websockets: bool,
pub websocket_ping: bool,
pub websocket_headers: bool,
pub wait_for_connectivity: bool,
}Expand description
What a backend can do. The client consults it to decide what it must do itself, and apps can
read it (day_part_http::capabilities()) to say what a platform offers.
Fields§
§streaming: boolResponse bodies arrive in chunks, pulled on demand.
upload_streaming: boolA request body can be sent from a reader without buffering it first.
upload_progress: boolUpload progress is reported while a body is sent.
manual_redirects: boolThe stack hands back redirect responses, so the client can follow and approve each hop.
auth_questions: boolThe stack asks about HTTP challenges itself (Question::Auth).
native_auth_schemes: boolNTLM and Negotiate are answered by the stack.
server_trust: boolThe stack reports each server certificate chain for evaluation (Question::ServerTrust).
client_identity: boolA client certificate identity can be presented.
The platform’s own cookie store is available.
platform_cache: boolThe platform’s own HTTP cache is available.
metrics: boolTransfer metrics are reported.
websockets: boolWebSockets are available.
websocket_ping: boolA WebSocket can send an explicit ping.
websocket_headers: boolA WebSocket handshake can carry custom request headers.
wait_for_connectivity: boolRequests can wait for connectivity instead of failing at once.