httpwg/http-extensions Issues

Last updated Sep 13, 2025, 5:47:29 AM UTC.

This repository doesn't have the Priority: Eventually label that's used to mark an issue as triaged without giving it an SLO. Until that's added, this summary uses heuristics to guess if each issue has been triaged.

Untriaged

Try to triage issues within . [ More Info ]

Issue Title Within SLO On maintainers' plates for Time left Time past SLO
#779 Should Accept algorithm ignore parameters? ❌
#978 Secondary Cache Key ❌
#1389 Variants: Invalid SFV format for Variants field ❌
#1675 Erratum 6481: Discuss fallback in Security Considerations ❌
#1689 Authenticating incompatible alternative services ❌
#1690 Leave ALPN negotiation to ALPN ❌
#1692 Alt-Svc and HTTPS records ❌
#1693 Alt-Svc and ECH ❌
#1694 Security implications of Alt-Svc fallback ❌
#2076 Request headers that aren't present ❌
#2077 What happens when variants changes? ❌
#2091 Variants: Confused Variant-key example ❌
#2093 Variants: typo on Appendix ❌
#2502 Update terminology once whatwg/html#8463 is fixed ❌
#2528 Mention fallback in SC ❌
#2592 [Proxy Alias] DNS name escaping ❌
#2751 Re-implement same-site redirect chain consideration ❌
#2840 Request and secondary certificate correlation ❌
#2978 Retrofit: X-Content-Type-Options is a list, not an item ❌
#3009 rfc6265bis: SAMESITE reference ❌
#3113 Cookies: local and server clock out-of-sync ❌
#3128 Purpose of the server algorithm ❌
#3164 RESUMABLE: resources do not manage things ❌
#3169 RESUMABLE: proposed rename section headers discussing state concepts ❌
#3170 RESUMABLE: definition of Upload-Length for both requests and responses is unclear ❌
#3172 RESUMABLE: proposal to relax the requirements on changes to limits ❌
#3173 RESUMABLE: text about defined/undefined Upload-Limit dict entries is unclear ❌
#3181 RESUMABLE: the term resource is under-specified in Section 4.2.2 ❌
#3182 RESUMABLE: the term "necessary fields" is overly vague ❌
#3184 RESUMABLE: upload creation server behaviour text is confusing ❌
#3186 RESUMABLE: proposal - change the design from server-managed to client-managed ❌
#3189 RESUMABLE: wording of "upload resource SHOULD generate" is "awkward" and "wrong" ❌
#3194 Denote Cookie Default Path as reusable algorithm ❌
#3209 RESUMABLE: server's support for resumable uploads would be better stated as resource's support ❌
#3211 RESUMABLE: might be clearer to state a server processes rather than receives portions of an upload ❌
#3212 RESUMABLE: is the upload-length superfluous for certain requests? ❌
#3215 RESUMABLE: thoughts on Prior Knowledge ❌
#3217 RESUMABLE: section 4 should add forward ref to section 13 ❌
#3218 RESUMABLE: how does an upload resource lose representation data? ❌
#3220 RESUMABLE: stopping a request in mid-transfer has some version-specific complexities ❌
#3221 RESUMABLE: 4.2.3 example D strikes as strange ❌
#3223 RESUMABLE: "after rejecting the offset" appears to be an undefined client action ❌
#3224 RESUMABLE: In 4.4.1, the third and fourth paragraphs conflict ❌
#3227 RESUMABLE: consider splitting some text out Section 4.4 (append) to keep focus on interim exchanges ❌
#3228 RESUMABLE: Section 10.1 description of how to use Repr-Digest seems wrong ❌
#3229 RESUMABLE: example of"appropriate header field" might be useful ❌
#3230 RESUMABLE: when appending and the offset matches the upload length, clarify what the server does ❌