net/http/httptrace: GotFirstResponseByte can fire twice for HTTP/2 after 100-continue response #15777
Labels
Documentation
FrozenDueToAge
help wanted
NeedsFix
The path to resolution is known, but the work has not been done.
Milestone
I just noticed that the httptrace.ClientTrace.GotFirstResponseByte hook can fire twice for HTTP/2 connections when the client sent an "Expect: 100-continue" request.
The standard library's net/http tests should check for exactly one occurrence of the substrings in TestTransportEventTrace*, and the http2 code should track whether it already called that hook.
I disappear for a month starting in a few hours. Maybe somebody can fix for 1.7. If not, low priority. Maybe it could even be documented instead for now.
/cc @tombergan (who doesn't care about HTTP/2 I don't think) and @adg
The text was updated successfully, but these errors were encountered: