Struct trust_dns_https::HttpsSerialResponse[][src]

#[must_use = "futures do nothing unless polled"]
pub struct HttpsSerialResponse(_);

A future that will resolve to a DnsResponse upon completion

Trait Implementations

impl Future for HttpsSerialResponse
[src]

The type of value that this future will resolved with if it is successful. Read more

The type of error that this future will resolve with if it fails in a normal fashion. Read more

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.

Block the current thread until this future is resolved. Read more

Map this future's result to a different type, returning a new future of the resulting type. Read more

Map this future's error to a different error, returning a new future. Read more

Map this future's error to any error implementing From for this future's Error, returning a new future. Read more

Chain on a computation for when a future finished, passing the result of the future to the provided closure f. Read more

Execute another future after this one has resolved successfully. Read more

Execute another future if this one resolves with an error. Read more

Waits for either one of two futures to complete. Read more

Waits for either one of two differently-typed futures to complete. Read more

Joins the result of two futures, waiting for them both to complete. Read more

Same as join, but with more futures.

Same as join, but with more futures.

Same as join, but with more futures.

Convert this future into a single element stream. Read more

Flatten the execution of this future when the successful result of this future is itself another future. Read more

Flatten the execution of this future when the successful result of this future is a stream. Read more

Fuse a future such that poll will never again be called once it has completed. Read more

Do something with the item of a future, passing it on. Read more

Catches unwinding panics while polling the future. Read more

Create a cloneable handle to this future where all handles will resolve to the same result. Read more

Auto Trait Implementations