Hello! On Fri, May 12, 2023 at 03:37:52AM +0100, J Carter wrote:
> # HG changeset patch > # User jordanc.car...@outlook.com > # Date 1683858766 -3600 > # Fri May 12 03:32:46 2023 +0100 > # Node ID de1a1b4141e827984cbd0d2feb97f870c32ff289 > # Parent b71e69247483631bd8fc79a47cc32b762625b1fb > Added $http2_stream_id > > Useful for tracing multiplexed requests from client logs or pcaps > captured between client and nginx, to nginx's own access logs. > > Also useful for matching multiplexed request's access log entries to > debug level error logs - which is particularly difficult to do. Thanks for the patch, but I would rather not. Consider using $connection_requests variable to identify individual requests within a connection, or the $request_id variable to identify requests globally. These do no depend on the particular protocol used and can be universally used for both HTTP/1.x and HTTP/2. -- Maxim Dounin http://mdounin.ru/ _______________________________________________ nginx-devel mailing list nginx-devel@nginx.org https://mailman.nginx.org/mailman/listinfo/nginx-devel
