You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
IIUC, h2o has two modes, identified by the special argument "quic." If set, it logs QUIC and HTTP events. If not, it logs HTTP events only. The limitation of the approach is that it is not capable of logging QUIC events only (therefore it cannot be used for tracing other applications using quicly). The other problem is that it does not trace TLS events.
I think that things would become clearer if there were three options to designate tracing at each layer. E.g., -H for HTTP-level tracing, -Q for QUIC level, -T for TLS-level.
The text was updated successfully, but these errors were encountered:
kazuho
changed the title
Better options for choosing what to log
Better options for choosing what to trace
Jun 8, 2020
IIUC, h2o has two modes, identified by the special argument "quic." If set, it logs QUIC and HTTP events. If not, it logs HTTP events only. The limitation of the approach is that it is not capable of logging QUIC events only (therefore it cannot be used for tracing other applications using quicly). The other problem is that it does not trace TLS events.
I think that things would become clearer if there were three options to designate tracing at each layer. E.g.,
-H
for HTTP-level tracing,-Q
for QUIC level,-T
for TLS-level.The text was updated successfully, but these errors were encountered: