Expand description
Server implementation of the HTTP/2.0 protocol.
Getting started
Running an HTTP/2.0 server requires the caller to manage accepting the connections as well as getting the connections to a state that is ready to begin the HTTP/2.0 handshake. See here for more details.
This could be as basic as using Tokio’s TcpListener to accept
connections, but usually it means using either ALPN or HTTP/1.1 protocol
upgrades.
Once a connection is obtained, it is passed to handshake,
which will begin the HTTP/2.0 handshake. This returns a future that
completes once the handshake process is performed and HTTP/2.0 streams may
be received.
handshake uses default configuration values. There are a number of
settings that can be changed by using Builder instead.
Inbound streams
The Connection instance is used to accept inbound HTTP/2.0 streams. It
does this by implementing futures::Stream. When a new stream is
received, a call to Connection::poll will return (request, response).
The request handle (of type http::Request<RecvStream>) contains the
HTTP request head as well as provides a way to receive the inbound data
stream and the trailers. The response handle (of type SendStream)
allows responding to the request, stream the response payload, send
trailers, and send push promises.
The send (SendStream) and receive (RecvStream) halves of the stream
can be operated independently.
Managing the connection
The Connection instance is used to manage connection state. The caller
is required to call either Connection::poll or
Connection::poll_close in order to advance the connection state. Simply
operating on SendStream or RecvStream will have no effect unless the
connection state is advanced.
It is not required to call both Connection::poll and
Connection::poll_close. If the caller is ready to accept a new stream,
then only Connection::poll should be called. When the caller does
not want to accept a new stream, Connection::poll_close should be
called.
The Connection instance should only be dropped once
Connection::poll_close returns Ready. Once Connection::poll
returns Ready(None), there will no longer be any more inbound streams. At
this point, only Connection::poll_close should be called.
Shutting down the server
Graceful shutdown of the server is not yet implemented.
Example
A basic HTTP/2.0 server example that runs over TCP and assumes prior knowledge, i.e. both the client and the server assume that the TCP socket will use the HTTP/2.0 protocol without prior negotiation.
extern crate futures;
extern crate h2;
extern crate http;
extern crate tokio;
use futures::{Future, Stream};
use h2::server;
use http::{Response, StatusCode};
use tokio::net::TcpListener;
pub fn main () {
let addr = "127.0.0.1:5928".parse().unwrap();
let listener = TcpListener::bind(&addr,).unwrap();
tokio::run({
// Accept all incoming TCP connections.
listener.incoming().for_each(move |socket| {
// Spawn a new task to process each connection.
tokio::spawn({
// Start the HTTP/2.0 connection handshake
server::handshake(socket)
.and_then(|h2| {
// Accept all inbound HTTP/2.0 streams sent over the
// connection.
h2.for_each(|(request, mut respond)| {
println!("Received request: {:?}", request);
// Build a response with no body
let response = Response::builder()
.status(StatusCode::OK)
.body(())
.unwrap();
// Send the response back to the client
respond.send_response(response, true)
.unwrap();
Ok(())
})
})
.map_err(|e| panic!("unexpected error = {:?}", e))
});
Ok(())
})
.map_err(|e| panic!("failed to run HTTP/2.0 server: {:?}", e))
});
}Structs
Builds server connections with custom configuration values.
Accepts inbound HTTP/2.0 streams on a connection.
In progress HTTP/2.0 connection handshake future.
Send a response back to the client
Functions
Creates a new configured HTTP/2.0 server with default configuration
values backed by io.