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
Add size limiter to New features or enhancements
needs implementer interest
Moving the issue forward requires implementers to express interest
topic: api
Body#formData
method
addition/proposal
#1592
opened Jan 12, 2023 by
lucacasonato
Clarify why omitting CORS headers in the preflight response helps against side-channel attacks
#1588
opened Jan 9, 2023 by
jub0bs
Missing tags in create a connection
clarification
Standard could be clearer
#1571
opened Dec 14, 2022 by
dlrobertson
Rename "extract-value flag" to "extract-value" and define it as a boolean
clarification
Standard could be clearer
#1567
opened Dec 11, 2022 by
dlrobertson
Can we consolidate initiator and initiator type? And potentially destination?
clarification
Standard could be clearer
#1563
opened Dec 9, 2022 by
annevk
Create Rage header section in HTTP extensions section
topic: http
#1553
opened Nov 27, 2022 by
dlrobertson
Specify exception to redirect-tainting: Upgrade-Insecure-Requests (UIR) and HSTS scheme upgrades
#1551
opened Nov 26, 2022 by
Rob--W
Add Standard could be clearer
good first issue
Ideal for someone new to a WHATWG standard or software project
<div algorithm>
wrappers around algorithms
clarification
#1526
opened Nov 3, 2022 by
jgraham
Option to fetch raw byte as is. (without decompressing)
addition/proposal
New features or enhancements
needs implementer interest
Moving the issue forward requires implementers to express interest
#1524
opened Nov 1, 2022 by
jimmywarting
The end of fetch response handover needs to operate on the internal response
clarification
Standard could be clearer
#1512
opened Oct 24, 2022 by
annevk
"set authorizationValue to authentication entry" is insufficiently precise
clarification
Standard could be clearer
#1497
opened Sep 30, 2022 by
domenic
Chromium's implementation of use-URL-credentials probably does not match the spec
interop
Implementations are not interoperable with each other
needs tests
Moving the issue forward requires someone to write tests
#1496
opened Sep 30, 2022 by
domenic
Prevent fetching from IPv4-mapped IPv6 addresses
topic: connections
#1492
opened Sep 22, 2022 by
letitz
Consider if redirect tainting should apply to Standard could be clearer
topic: timing
Issues and PR that touch on the infrastructure that is used by ResourceTiming, NavigationTiming, etc
Timing-Allow-Origin
clarification
#1484
opened Sep 5, 2022 by
noamr
Feature detecting streaming requests
topic: streams
upload-streaming-blocking
#1470
opened Jul 12, 2022 by
jakearchibald
Update Note on Request Destination / CSP directive
clarification
Standard could be clearer
good first issue
Ideal for someone new to a WHATWG standard or software project
#1466
opened Jul 6, 2022 by
evilpie
Add Standard could be clearer
initiatorType
values to CSP/destination table
clarification
#1452
opened Jun 14, 2022 by
noamr
Proposal: Expose New features or enhancements
needs implementer interest
Moving the issue forward requires implementers to express interest
initiator
to JavaScript
addition/proposal
#1430
opened Apr 29, 2022 by
d3lm
Define HSTS as "internal" redirect
security/privacy
There are security or privacy implications
topic: redirects
#1426
opened Apr 19, 2022 by
annevk
Proposal: CORS means TAO by default
addition/proposal
New features or enhancements
topic: cors
#1414
opened Mar 17, 2022 by
noamr
Previous Next
ProTip!
Exclude everything labeled
bug
with -label:bug.