- From: Anne van Kesteren <notifications@github.com>
- Date: Tue, 18 Nov 2025 04:51:23 -0800
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 18 November 2025 12:51:27 UTC
@annevk commented on this pull request.
This looks good modulo nits. One question: the WebTransport handshake doesn't have the 101 response handling?
> +<h3 class=no-num id=webtransport-protocol>WebTransport</h3>
+
+<p>As part of establishing a connection, the {{WebTransport}} object initiates a special kind of
+<a for=/>fetch</a> (using a <a for=/>request</a> whose <a for=request>mode</a> is
+"<code>webtransport</code>") which allows it to share in many fetch policy decisions, such
+<cite>HTTP Strict Transport Security (HSTS)</cite>. Ultimately this results in fetch calling into
+<cite>WebTransport</cite> which in turn <a lt="obtain a connection">obtains a connection</a>.
+[[WEBTRANSPORT]][[HSTS]]
+
+<p class=note><cite>WebTransport</cite> needs to wrap the <a>obtain a connection</a>
+algorithm to add features unique to WebTransport, like
+{{WebTransportOptions/serverCertificateHashes}}. [[WEBTRANSPORT]]
I think we can omit this section and leave explaining this entirely to WebTransport. We have a section on WebSockets only because part of it was historically defined in Fetch.
--
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/pull/1873#pullrequestreview-3477669464
You are receiving this because you are subscribed to this thread.
Message ID: <whatwg/fetch/pull/1873/review/3477669464@github.com>
Received on Tuesday, 18 November 2025 12:51:27 UTC