Skip to content

Add details as to why webtransport spec modifications are not required. #102

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.

Sign up for GitHub

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

Merged
hubertchao merged 1 commit into from
Feb 25, 2026
Merged

Add details as to why webtransport spec modifications are not required. #102

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion index.bs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -803,13 +803,19 @@ required beyond the fetch change proposed above.
One minor difference between the Fetch API and the WebSockets API is that
WebSockets does not have an equivalent to fetch's `RequestInit`, and so there
is no place to put in a `targetAddressSpace` option to bypass mixed content
checks for ws:// urls.
checks for ws:// urls.

## Integration with WebTransport ## {#integration-with-webtransport}

WebTransport connections should be subject to the same local network access
permission requirements.

No modification to the WebTransport spec will be required. In the WebTransport
spec, [obtaining a WebTransport
connection](https://www.w3.org/TR/webtransport/#obtain-a-webtransport-connection)
references the Fetch spec for obtaining a connection in step 6, which is being
modified in [[#fetching]]

## Integration with HTML ## {#integration-with-html}

To support the checks in [[FETCH]], user agents must remember the source IP
Expand Down