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
We now support both HTTP Upgrades (#1126) and CONNECT (#1200). They both make use of the HTTP sensors while the requests look like HTTP/1, and once the upgrade is complete, they convert into TCP proxies. That means no more HTTP sensors are used, but the transport sensors are still in place.
However, these are both probably significant enough to warrant emitting special events in our telemetry, so that users can see successful (and failed) HTTP Upgrades / CONNECT. Or maybe just Upgrades are sufficiently important.
A related question is whether something should be exposed in TAP.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.
We now support both HTTP Upgrades (#1126) and CONNECT (#1200). They both make use of the HTTP sensors while the requests look like HTTP/1, and once the upgrade is complete, they convert into TCP proxies. That means no more HTTP sensors are used, but the transport sensors are still in place.
However, these are both probably significant enough to warrant emitting special events in our telemetry, so that users can see successful (and failed) HTTP Upgrades / CONNECT. Or maybe just Upgrades are sufficiently important.
A related question is whether something should be exposed in TAP.
The text was updated successfully, but these errors were encountered: