Update man pages
This commit is contained in:
parent
c4fba5139c
commit
50083f0d22
|
@ -1,6 +1,6 @@
|
|||
.\" 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
|
||||
h2load \- HTTP/2 benchmarking tool
|
||||
.
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
.\" 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
|
||||
nghttp \- HTTP/2 client
|
||||
.
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
.\" 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
|
||||
nghttpd \- HTTP/2 server
|
||||
.
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
.\" 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
|
||||
nghttpx \- HTTP/2 proxy
|
||||
.
|
||||
|
@ -129,13 +129,12 @@ value. Each parameter is described as follows.
|
|||
.sp
|
||||
The backend application protocol can be specified using
|
||||
optional "proto" parameter, and in the form of
|
||||
"proto=<PROTO>". All that share the same <PATTERN> must
|
||||
have the same <PROTO> value if it is given. <PROTO>
|
||||
should be one of the following list without quotes:
|
||||
"h2", "http/1.1". The default value of <PROTO> is
|
||||
"http/1.1". Note that usually "h2" refers to HTTP/2
|
||||
over TLS. But in this option, it may mean HTTP/2 over
|
||||
cleartext TCP unless "tls" keyword is used (see below).
|
||||
"proto=<PROTO>". <PROTO> should be one of the following
|
||||
list without quotes: "h2", "http/1.1". The default
|
||||
value of <PROTO> is "http/1.1". Note that usually "h2"
|
||||
refers to HTTP/2 over TLS. But in this option, it may
|
||||
mean HTTP/2 over cleartext TCP unless "tls" keyword is
|
||||
used (see below).
|
||||
.sp
|
||||
TLS can be enabled by specifying optional "tls"
|
||||
parameter. TLS is not enabled by default.
|
||||
|
|
|
@ -113,13 +113,12 @@ Connections
|
|||
|
||||
The backend application protocol can be specified using
|
||||
optional "proto" parameter, and in the form of
|
||||
"proto=<PROTO>". All that share the same <PATTERN> must
|
||||
have the same <PROTO> value if it is given. <PROTO>
|
||||
should be one of the following list without quotes:
|
||||
"h2", "http/1.1". The default value of <PROTO> is
|
||||
"http/1.1". Note that usually "h2" refers to HTTP/2
|
||||
over TLS. But in this option, it may mean HTTP/2 over
|
||||
cleartext TCP unless "tls" keyword is used (see below).
|
||||
"proto=<PROTO>". <PROTO> should be one of the following
|
||||
list without quotes: "h2", "http/1.1". The default
|
||||
value of <PROTO> is "http/1.1". Note that usually "h2"
|
||||
refers to HTTP/2 over TLS. But in this option, it may
|
||||
mean HTTP/2 over cleartext TCP unless "tls" keyword is
|
||||
used (see below).
|
||||
|
||||
TLS can be enabled by specifying optional "tls"
|
||||
parameter. TLS is not enabled by default.
|
||||
|
|
Loading…
Reference in New Issue