Document PROX protocol and PSK in nghttpx howto
This commit is contained in:
parent
175001a8d9
commit
41d8a3ac09
|
@ -370,6 +370,61 @@ parameter in :option:`--backend` option, like so:
|
||||||
nghttpx will cache resolved addresses for certain period of time. To
|
nghttpx will cache resolved addresses for certain period of time. To
|
||||||
change this cache period, use :option:`--dns-cache-timeout`.
|
change this cache period, use :option:`--dns-cache-timeout`.
|
||||||
|
|
||||||
|
Enable PROXY protocol
|
||||||
|
---------------------
|
||||||
|
|
||||||
|
PROXY protocol can be enabled per frontend. In order to enable PROXY
|
||||||
|
protocol, use ``proxyproto`` parameter in :option:`--frontend` option,
|
||||||
|
like so:
|
||||||
|
|
||||||
|
.. code-block:: text
|
||||||
|
|
||||||
|
frontend=*,443;proxyproto
|
||||||
|
|
||||||
|
PSK cipher suites
|
||||||
|
-----------------
|
||||||
|
|
||||||
|
nghttpx supports pre-shared key (PSK) cipher suites for both frontend
|
||||||
|
and backend TLS connections. For frontend connection, use
|
||||||
|
:option:`--psk-secrets` option to specify a file which contains PSK
|
||||||
|
identity and secrets. The format of the file is
|
||||||
|
``<identity>:<hex-secret>``, where ``<identity>`` is PSK identity, and
|
||||||
|
``<hex-secret>`` is PSK secret in hex, like so:
|
||||||
|
|
||||||
|
.. code-block:: text
|
||||||
|
|
||||||
|
client1:9567800e065e078085c241d54a01c6c3f24b3bab71a606600f4c6ad2c134f3b9
|
||||||
|
client2:b1376c3f8f6dcf7c886c5bdcceecd1e6f1d708622b6ddd21bda26ebd0c0bca99
|
||||||
|
|
||||||
|
nghttpx server accepts any of the identity and secret pairs in the
|
||||||
|
file. The default cipher suite list does not contain PSK cipher
|
||||||
|
suites. In order to use PSK, PSK cipher suite must be enabled by
|
||||||
|
using :option:`--ciphers` option. The desired PSK cipher suite may be
|
||||||
|
listed in `HTTP/2 cipher black list
|
||||||
|
<https://tools.ietf.org/html/rfc7540#appendix-A>`_. In order to use
|
||||||
|
such PSK cipher suite with HTTP/2, disable HTTP/2 cipher black list by
|
||||||
|
using :option:`--no-http2-cipher-black-list` option. But you should
|
||||||
|
understand its implications.
|
||||||
|
|
||||||
|
For backend connection, use :option:`--client-psk-secrets` option to
|
||||||
|
specify a file which contains single PSK identity and secret. The
|
||||||
|
format is the same as the file used by :option:`--psk-secrets`
|
||||||
|
described above, but only first identity and secret pair is solely
|
||||||
|
used, like so:
|
||||||
|
|
||||||
|
.. code-block:: text
|
||||||
|
|
||||||
|
client2:b1376c3f8f6dcf7c886c5bdcceecd1e6f1d708622b6ddd21bda26ebd0c0bca99
|
||||||
|
|
||||||
|
The default cipher suite list does not contain PSK cipher suites. In
|
||||||
|
order to use PSK, PSK cipher suite must be enabled by using
|
||||||
|
:option:`--client-ciphers` option. The desired PSK cipher suite may
|
||||||
|
be listed in `HTTP/2 cipher black list
|
||||||
|
<https://tools.ietf.org/html/rfc7540#appendix-A>`_. In order to use
|
||||||
|
such PSK cipher suite with HTTP/2, disable HTTP/2 cipher black list by
|
||||||
|
using :option:`--client-no-http2-cipher-black-list` option. But you
|
||||||
|
should understand its implications.
|
||||||
|
|
||||||
Migration from nghttpx v1.18.x or earlier
|
Migration from nghttpx v1.18.x or earlier
|
||||||
-----------------------------------------
|
-----------------------------------------
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue