Struct hickory_proto::h2::HttpsClientStream

pub struct HttpsClientStream { /* private fields */ }

Available on crate feature dns-over-https only.

A DNS client connection for DNS-over-HTTPS

Trait Implementations

impl Clone for HttpsClientStream

fn clone(&self) -> HttpsClientStream

Returns a copy of the value.

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

Performs copy-assignment from source.

impl Display for HttpsClientStream

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

Formats the value using the given formatter.

impl DnsRequestSender for HttpsClientStream

fn send_message(&mut self, message: DnsRequest) -> DnsResponseStream

This indicates that the HTTP message was successfully sent, and we now have the response.RecvStream

If the request fails, this will return the error, and it should be assumed that the Stream portion of this will have no date.

5.2.  The HTTP Response

   An HTTP response with a 2xx status code ([RFC7231] Section 6.3)
   indicates a valid DNS response to the query made in the HTTP request.
   A valid DNS response includes both success and failure responses.
   For example, a DNS failure response such as SERVFAIL or NXDOMAIN will
   be the message in a successful 2xx HTTP response even though there
   was a failure at the DNS layer.  Responses with non-successful HTTP
   status codes do not contain DNS answers to the question in the
   corresponding request.  Some of these non-successful HTTP responses
   (e.g., redirects or authentication failures) could mean that clients
   need to make new requests to satisfy the original question.

   Different response media types will provide more or less information
   from a DNS response.  For example, one response type might include
   the information from the DNS header bytes while another might omit
   it.  The amount and type of information that a media type gives is
   solely up to the format, and not defined in this protocol.

   The only response type defined in this document is "application/dns-
   message", but it is possible that other response formats will be
   defined in the future.

   The DNS response for "application/dns-message" in Section 7 MAY have
   one or more EDNS options [RFC6891], depending on the extension
   definition of the extensions given in the DNS request.

   Each DNS request-response pair is matched to one HTTP exchange.  The
   responses may be processed and transported in any order using HTTP's
   multi-streaming functionality ([RFC7540] Section 5).

   Section 6.1 discusses the relationship between DNS and HTTP response
   caching.

   A DNS API server MUST be able to process application/dns-message
   request messages.

   A DNS API server SHOULD respond with HTTP status code 415
   (Unsupported Media Type) upon receiving a media type it is unable to
   process.

fn shutdown(&mut self)

Allows the upstream user to inform the underling stream that it should shutdown.

fn is_shutdown(&self) -> bool

Returns true if the stream has been shutdown with shutdown

impl Stream for HttpsClientStream

type Item = Result<(), ProtoError>

Values yielded by the stream.

fn poll_next( self: Pin<&mut Self>, cx: &mut Context<'_> ) -> Poll<Option<Self::Item>>

Attempt to pull out the next value of this stream, registering the current task for wakeup if the value is not yet available, and returning None if the stream is exhausted.

fn size_hint(&self) -> (usize, Option<usize>)

Returns the bounds on the remaining length of the stream.