Issues: whatwg/fetch
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Milestones
Assignee
Sort
Issues list
Define what consequences NULL bytes (0x00) or other invalid values in header names have
#1747
opened Apr 16, 2024 by
JannisBush
[render-blocking] The links of "render-blocking" in fetch are vague
#1746
opened Apr 12, 2024 by
cathiechen
Add compression dictionary negotiation and decoding to the fetch processing model
addition/proposal
New features or enhancements
needs concrete proposal
Moving the issue forward requires someone to figure out a detailed plan
#1739
opened Feb 26, 2024 by
pmeenan
add a method to get a Uint8Array to Body
addition/proposal
New features or enhancements
needs concrete proposal
Moving the issue forward requires someone to figure out a detailed plan
topic: api
#1732
opened Jan 29, 2024 by
bakkot
Automatic decompression should sanitize Moving the issue forward requires implementers to express interest
needs tests
Moving the issue forward requires someone to write tests
topic: http
Content-Encoding
and Content-Length
headers from the response
needs implementer interest
#1729
opened Dec 21, 2023 by
lucacasonato
Referrer determination should be done on updated URLs in main fetch
#1727
opened Dec 14, 2023 by
meacer
RequestInit::priority lacks corresponding Request::priority attribute
#1726
opened Dec 2, 2023 by
saschanaz
Incremental read: Why only Uint8Array instead of BufferSource?
#1724
opened Nov 16, 2023 by
saschanaz
API for receiving interim responses (including early hints)
addition/proposal
New features or enhancements
needs implementer interest
Moving the issue forward requires implementers to express interest
#1716
opened Oct 2, 2023 by
jasnell
"should X be blocked" is a bad pattern
clarification
Standard could be clearer
#1714
opened Sep 29, 2023 by
annevk
Tighten
application/x-www-form-urlencoded
CORS safe-list carveout?
topic: cors
#1706
opened Sep 26, 2023 by
domfarolino
Consider restricting 103 Early Hints to HTTP/2 or later
topic: http
#1698
opened Aug 30, 2023 by
tunetheweb
Previous Next
ProTip!
no:milestone will show everything without a milestone.