[net] http2: add support for setting RFC 9218 priority via header field

3 views
Skip to first unread message

Nicholas Husin (Gerrit)

unread,
Dec 10, 2025, 3:38:26 PM (11 days ago) Dec 10
to goph...@pubsubhelper.golang.org, Damien Neil, Go LUCI, golang-co...@googlegroups.com
Attention needed from Damien Neil

New activity on the change

Open in Gerrit

Related details

Attention is currently required from:
  • Damien Neil
Submit Requirements:
  • requirement is not satisfiedCode-Review
  • requirement satisfiedNo-Unresolved-Comments
  • requirement is not satisfiedReview-Enforcement
  • requirement is not satisfiedTryBots-Pass
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. DiffyGerrit
Gerrit-MessageType: comment
Gerrit-Project: net
Gerrit-Branch: master
Gerrit-Change-Id: I6dc409b650fd52fa192d771a16b7a4ac5e51c9aa
Gerrit-Change-Number: 729120
Gerrit-PatchSet: 2
Gerrit-Owner: Nicholas Husin <n...@golang.org>
Gerrit-Reviewer: Damien Neil <dn...@google.com>
Gerrit-Reviewer: Nicholas Husin <n...@golang.org>
Gerrit-Attention: Damien Neil <dn...@google.com>
Gerrit-Comment-Date: Wed, 10 Dec 2025 20:38:22 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: No
unsatisfied_requirement
satisfied_requirement
open
diffy

Damien Neil (Gerrit)

unread,
Dec 19, 2025, 6:05:22 PM (2 days ago) Dec 19
to Nicholas Husin, goph...@pubsubhelper.golang.org, Go LUCI, golang-co...@googlegroups.com
Attention needed from Nicholas Husin

Damien Neil added 3 comments

File http2/server.go
Line 2087, Patchset 2 (Latest): // Round-robin behavior.
Damien Neil . unresolved

Perhaps expand on the reason for ignoring the priority in this case?

Line 2207, Patchset 2 (Latest): }
Damien Neil . unresolved

If this is a user-provided write scheduler we still want to call `AdjustStream`. I think we should just always call `AdjustStream` on a PRIORITY frame, regardless of what the write scheduler is.

Line 2215, Patchset 2 (Latest): }
Damien Neil . unresolved

Should we handle PRIORITY_UPDATE frames when the request comes through a coalescing intermediary? The "Priority" header is under control of the originator of the request unless the intermediary strips it, but forwarding a PRIORITY_UPDATE frame is more intentional.

Maybe we should only ignore Priority headers but not PRIORITY_UPDATE frames?

Open in Gerrit

Related details

Attention is currently required from:
  • Nicholas Husin
Submit Requirements:
    • requirement is not satisfiedCode-Review
    • requirement is not satisfiedNo-Unresolved-Comments
    • requirement is not satisfiedReview-Enforcement
    • requirement satisfiedTryBots-Pass
    Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. DiffyGerrit
    Gerrit-MessageType: comment
    Gerrit-Project: net
    Gerrit-Branch: master
    Gerrit-Change-Id: I6dc409b650fd52fa192d771a16b7a4ac5e51c9aa
    Gerrit-Change-Number: 729120
    Gerrit-PatchSet: 2
    Gerrit-Owner: Nicholas Husin <n...@golang.org>
    Gerrit-Reviewer: Damien Neil <dn...@google.com>
    Gerrit-Reviewer: Nicholas Husin <n...@golang.org>
    Gerrit-Attention: Nicholas Husin <n...@golang.org>
    Gerrit-Comment-Date: Fri, 19 Dec 2025 23:05:18 +0000
    Gerrit-HasComments: Yes
    Gerrit-Has-Labels: No
    unsatisfied_requirement
    satisfied_requirement
    open
    diffy
    Reply all
    Reply to author
    Forward
    0 new messages