Dragana Damjanovic

I think that you want to look for an extended connect only. And then have the extended connect code decide which event to dispatch. _Originally posted by @martinthomson in https://github.com/mozilla/neqo/pull/1252#discussion_r725736621_

https://datatracker.ietf.org/doc/html/draft-ietf-webtrans-http3#section-6

See section [5](https://datatracker.ietf.org/doc/html/draft-ietf-webtrans-http3-03#section-5).

I think our WebTransport implementation behaves according to the spec regarding the GOAWAY frame, but we should add tests.

We need a client for quick interop testing. We should write a server as well.

There are 2 cases for this: - when the server respond with 404 it does not close the receiving side of the request. If it do that the reset may...

Propagating RESET error codes for an unknown stream

1

Spec [section 4.3](https://datatracker.ietf.org/doc/html/draft-ietf-webtrans-http3-03#section-4.3): > If a WebTransport implementation intentionally allows only one session over a given HTTP/3 connection, it SHALL forward the error codes within WebTransport application error code range...

See https://crash-stats.mozilla.org/search/?release_channel=release&signature=%3Dneqo_transport%3A%3Aconnection%3A%3AConnection%3A%3Ainput_path&product=Firefox&date=%3E%3D2022-09-02T00%3A00%3A00.000Z&date=%3C2022-10-04T14%3A46%3A00.000Z&_facets=install_time&_facets=version&_facets=address&_facets=moz_crash_reason&_facets=reason&_facets=build_id&_facets=platform_pretty_version&_facets=signature&_facets=useragent_locale&_sort=-date&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#crash-reports See bug [1750978](https://bugzilla.mozilla.org/show_bug.cgi?id=1750978)