Home /Modules/http-servers/LOGGING.md

LOGGING.md

http-servers/LOGGING.md · 60 line(s) · markdown

HTTP Server Logging

General rule

HTTP server logs are operational records, not copies of request bodies. The server implementations should avoid logging request bodies, credentials, private keys, or complete query strings as routine operational data.

Current logging boundary

GradeDefault logging destinationNotes
1configured log destination / standard error according to server optionsHTTP/1 operational logging
2standard errorNative HTTP/2 stream-aware diagnostics
3standard errorSLeeLa adapter and QUIC backend diagnostics

Grade 3 currently inherits the wsslserver backend's standard error stream. The adapter does not create a second hidden HTTP/3 log file.

A deployment may redirect or supervise standard error using its service manager. For example, systemd, a container runtime, or another process supervisor can collect the stream without changing the protocol implementation.

What should be logged

Recommended operational fields include:

Do not routinely log:

Log rotation and retention

Log rotation belongs to the deployment environment unless a specific server option explicitly implements it. Supervisors should bound disk consumption and retain enough records for operational diagnosis without turning ordinary HTTP logs into an unrestricted traffic archive.

HTTP/3 backend

The Grade 3 adapter reports its selected backend and startup parameters on standard error, then replaces its process image with the backend. Backend diagnostics therefore remain part of the same service log stream.