-
Notifications
You must be signed in to change notification settings - Fork 50
Issues: w3c/webtransport
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
Projects
Milestones
Assignee
Sort
Issues list
Is CORS preflight necessary for WebTransport if we add Header support?
Discuss at next meeting
Flags an issue to be discussed at the next WG working
#637
opened Mar 11, 2025 by
jan-ivar
Handshake is not defined in terms of Fetch
Discuss at next meeting
Flags an issue to be discussed at the next WG working
Consider removing serverCertificateHashes
Discuss at next meeting
Flags an issue to be discussed at the next WG working
Reference overview doc instead of HTTP3 doc in two places
Editorial
This is an editorial PR that can be merged by editors without discussion
Ready for PR
Should incomingUni/BidirectionalStreams be "owning"?
Waiting-for-feedback
Waiting on requested input or feedback
Can we feed the [[OutgoingDatagramsQueue]] without prematurely resolving write promises?
hard
Things to discuss and think about
Exposing headers of the CONNECT response
Discuss at next meeting
Flags an issue to be discussed at the next WG working
Do we want to allow web developers to add headers of the CONNECT request?
Discuss at next meeting
Flags an issue to be discussed at the next WG working
Write up a list of usability pitfalls (streams arriving out of order etc)
Editorial
This is an editorial PR that can be merged by editors without discussion
Ready for PR
Document that chunking boundaries aren't preserved in streams
Editorial
This is an editorial PR that can be merged by editors without discussion
Previous Next
ProTip!
Follow long discussions with comments:>50.