reuse of native libraries capabilities.
@item Modern, reliable, secure and fast TLS 1.3 implementation with
-ChaCha20-Poly1305, session resumption and GOST cryptography (if built
-with @url{http://www.gostls13.cypherpunks.ru/, gostls13}). SNI supported.
+ChaCha20-Poly1305, session resumption and SNI.
+
+@item If built with @url{http://www.gostls13.cypherpunks.ru/, gostls13},
+then @url{http://www.gost.cypherpunks.ru/, GOST} TLS 1.3 cryptography
+will be fully supported, with ability to use GOST-based X.509
+certificates if client announces its knowledge of GOST algorithms (with
+the fallback to ordinary ECDSA ones).
@item HTTP/1.1, @url{https://en.wikipedia.org/wiki/HTTP%2F2, HTTP/2}
(only when negotiated during ALPN) and keepalives support. Graceful
@item Auto-generated directory listings and
read-only @url{https://en.wikipedia.org/wiki/WebDAV, WebDAV} support.
+@item Per-domain HTTP basic authorization and TLS client authentication.
+
@item If corresponding @file{.meta4} files are found, then @code{Link}
header is generated automatically to that
@url{http://www.metalinker.org/, Metalink}.
@end itemize
-Basically all configuration is done directly inside source code.
+Basically all configuration is done directly inside source code. You
+have to recompile it every time configuration changes. Is it a problem?
+I doubt, because Go is very fast. But it produces huge statically linked
+executables, you say! Use @command{bsdiff}/@command{bspatch}!
+
+Send @code{SIGINFO} (@code{SIGUSR1} on Linux) signal to get current
+daemon's configuration.
+
Initially @command{godlighty} has basic static files handlers (with
compression, HTTP preconditions are enabled of course). In the example
below there are nearly all default functions.