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
{{ message }}
This repository has been archived by the owner on Feb 17, 2024. It is now read-only.
Our implementation of message tracing for HTTP currently breaks when the request or response does not contain a Content-Length header, but boundaries of messages in HTTP/1.1 may be defined by using the Transfer-Encoding header, or simply by closing the TCP stream.
We should have complete support for the HTTP/1.1 protocol to support tracing a wide range of applications.
The text was updated successfully, but these errors were encountered:
Our implementation of message tracing for HTTP currently breaks when the request or response does not contain a
Content-Length
header, but boundaries of messages in HTTP/1.1 may be defined by using theTransfer-Encoding
header, or simply by closing the TCP stream.We should have complete support for the HTTP/1.1 protocol to support tracing a wide range of applications.
The text was updated successfully, but these errors were encountered: