PUSH_PROMISE to initialize WebTransport connection?

[Chris Morris]

Initializing a WebTransport connection, after SETTINGS are exchanged, I'm receiving a bidirectional stream from the Chrome client, first byte 0x1 (PUSH stream), followed by what appears to be a Push ID (0x9) and then a PUSH_PROMISE (0x5) frame. I was expecting just a simple CONNECT request, which I'd send the 2xx OK back to to complete the connection. What's going on here?

Thanks

[Lucas Pardue]

Hi Chris,

I'm not a Chrome engineer but this doesn't sound right. Before a WebTransport session is up, client bidirectional streams are for HTTP/3 requests and they don't start with any type. So it's more feasible that the first byte is for the HEADERS frame type that contains the QPACK encoded request. A netlog or pcap should be able to illustrate.

Cheers 

Lucas

On Mon, 27 Dec 2021, 23:53 Chris Morris, <reynm...@gmail.com> wrote:

Initializing a WebTransport connection, after SETTINGS are exchanged, I'm receiving a bidirectional stream from the Chrome client, first byte 0x1 (PUSH stream), followed by what appears to be a Push ID (0x9) and then a PUSH_PROMISE (0x5) frame. I was expecting just a simple CONNECT request, which I'd send the 2xx OK back to to complete the connection. What's going on here?

Thanks

--
You received this message because you are subscribed to the Google Groups "web-transport-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to web-transport-...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/web-transport-dev/01918fe3-33f0-4453-93ce-f65e5ea833fdn%40chromium.org.