1695780 - Treat StatelessReset error differently

Status: RESOLVED FIXED

(Core :: Networking: HTTP, task, P2)

Comment 1

[Dragana Damjanovic [:dragana]]

We treat all error from neqo as a protocol error and we exclude domains from HTTP3 if we received such an error. This is done here.
There are some error that should be treated as netwok_interrupt or reset and also we should not exclude the domains from HTTP3. This errors are:
StatelessReset(from neqo (mapping is here)
and NO_ERROR errors (from neqo or from a peer app or transport error: CloseError::TransportError with code 0, CloseError::PeerError witth code 0, CloseError::PeerAppError with code 0x100, and CloseError::AppError with code 0x100).

Comment 2

[Dragana Damjanovic [:dragana]]

Error mappings forn neqo to neqo_glue are here and here

this is an example how these error codes are read in necko (c++) : https://searchfox.org/mozilla-central/rev/63fcc3f1a2cc73488d8986f4cf91fce2cd4b7564/netwerk/protocol/http/Http3Session.cpp#1676-1679

Comment 3

[Dragana Damjanovic [:dragana]]

We should use NET_ERROR_RESET so that transaction can be restarted if possible.

Comment 4

[Kershaw Chang [:kershaw]]

Attachment: Bug 1695780 - Make it possible to restart the transaction when having a StatelessReset error

Comment 5

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/f6eed285f801
Make it possible to restart the transaction when having a StatelessReset error r=necko-reviewers,dragana

Comment 6

[Natalia Csoregi [:nataliaCs]]

https://hg.mozilla.org/mozilla-central/rev/f6eed285f801