Commit 50083f0d authored by Tatsuhiro Tsujikawa's avatar Tatsuhiro Tsujikawa

Update man pages

parent c4fba513
.\" Man page generated from reStructuredText. .\" Man page generated from reStructuredText.
. .
.TH "H2LOAD" "1" "May 21, 2016" "1.11.0-DEV" "nghttp2" .TH "H2LOAD" "1" "May 26, 2016" "1.11.0" "nghttp2"
.SH NAME .SH NAME
h2load \- HTTP/2 benchmarking tool h2load \- HTTP/2 benchmarking tool
. .
......
.\" Man page generated from reStructuredText. .\" Man page generated from reStructuredText.
. .
.TH "NGHTTP" "1" "May 21, 2016" "1.11.0-DEV" "nghttp2" .TH "NGHTTP" "1" "May 26, 2016" "1.11.0" "nghttp2"
.SH NAME .SH NAME
nghttp \- HTTP/2 client nghttp \- HTTP/2 client
. .
......
.\" Man page generated from reStructuredText. .\" Man page generated from reStructuredText.
. .
.TH "NGHTTPD" "1" "May 21, 2016" "1.11.0-DEV" "nghttp2" .TH "NGHTTPD" "1" "May 26, 2016" "1.11.0" "nghttp2"
.SH NAME .SH NAME
nghttpd \- HTTP/2 server nghttpd \- HTTP/2 server
. .
......
.\" Man page generated from reStructuredText. .\" Man page generated from reStructuredText.
. .
.TH "NGHTTPX" "1" "May 21, 2016" "1.11.0-DEV" "nghttp2" .TH "NGHTTPX" "1" "May 26, 2016" "1.11.0" "nghttp2"
.SH NAME .SH NAME
nghttpx \- HTTP/2 proxy nghttpx \- HTTP/2 proxy
. .
...@@ -129,13 +129,12 @@ value. Each parameter is described as follows. ...@@ -129,13 +129,12 @@ value. Each parameter is described as follows.
.sp .sp
The backend application protocol can be specified using The backend application protocol can be specified using
optional "proto" parameter, and in the form of optional "proto" parameter, and in the form of
"proto=<PROTO>". All that share the same <PATTERN> must "proto=<PROTO>". <PROTO> should be one of the following
have the same <PROTO> value if it is given. <PROTO> list without quotes: "h2", "http/1.1". The default
should be one of the following list without quotes: value of <PROTO> is "http/1.1". Note that usually "h2"
"h2", "http/1.1". The default value of <PROTO> is refers to HTTP/2 over TLS. But in this option, it may
"http/1.1". Note that usually "h2" refers to HTTP/2 mean HTTP/2 over cleartext TCP unless "tls" keyword is
over TLS. But in this option, it may mean HTTP/2 over used (see below).
cleartext TCP unless "tls" keyword is used (see below).
.sp .sp
TLS can be enabled by specifying optional "tls" TLS can be enabled by specifying optional "tls"
parameter. TLS is not enabled by default. parameter. TLS is not enabled by default.
......
...@@ -113,13 +113,12 @@ Connections ...@@ -113,13 +113,12 @@ Connections
The backend application protocol can be specified using The backend application protocol can be specified using
optional "proto" parameter, and in the form of optional "proto" parameter, and in the form of
"proto=<PROTO>". All that share the same <PATTERN> must "proto=<PROTO>". <PROTO> should be one of the following
have the same <PROTO> value if it is given. <PROTO> list without quotes: "h2", "http/1.1". The default
should be one of the following list without quotes: value of <PROTO> is "http/1.1". Note that usually "h2"
"h2", "http/1.1". The default value of <PROTO> is refers to HTTP/2 over TLS. But in this option, it may
"http/1.1". Note that usually "h2" refers to HTTP/2 mean HTTP/2 over cleartext TCP unless "tls" keyword is
over TLS. But in this option, it may mean HTTP/2 over used (see below).
cleartext TCP unless "tls" keyword is used (see below).
TLS can be enabled by specifying optional "tls" TLS can be enabled by specifying optional "tls"
parameter. TLS is not enabled by default. parameter. TLS is not enabled by default.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment