2d2d5574a6
There are many changes involved with this, but let's just talk about
user-facing changes.
- Creating a `Client` and `Server` now needs a Tokio `Core` event loop
to attach to.
- `Request` and `Response` both no longer implement the
`std::io::{Read,Write}` traits, but instead represent their bodies as a
`futures::Stream` of items, where each item is a `Chunk`.
- The `Client.request` method now takes a `Request`, instead of being
used as a builder, and returns a `Future` that resolves to `Response`.
- The `Handler` trait for servers is no more, and instead the Tokio
`Service` trait is used. This allows interoperability with generic
middleware.
BREAKING CHANGE: A big sweeping set of breaking changes.
31 lines
944 B
Rust
31 lines
944 B
Rust
use method::Method;
|
|
|
|
header! {
|
|
/// `Access-Control-Request-Method` header, part of
|
|
/// [CORS](http://www.w3.org/TR/cors/#access-control-request-method-request-header)
|
|
///
|
|
/// The `Access-Control-Request-Method` header indicates which method will be
|
|
/// used in the actual request as part of the preflight request.
|
|
/// # ABNF
|
|
/// ```plain
|
|
/// Access-Control-Request-Method: \"Access-Control-Request-Method\" \":\" Method
|
|
/// ```
|
|
///
|
|
/// # Example values
|
|
/// * `GET`
|
|
///
|
|
/// # Examples
|
|
/// ```
|
|
/// use hyper::header::{Headers, AccessControlRequestMethod};
|
|
/// use hyper::Method;
|
|
///
|
|
/// let mut headers = Headers::new();
|
|
/// headers.set(AccessControlRequestMethod(Method::Get));
|
|
/// ```
|
|
(AccessControlRequestMethod, "Access-Control-Request-Method") => [Method]
|
|
|
|
test_access_control_request_method {
|
|
test_header!(test1, vec![b"GET"]);
|
|
}
|
|
}
|