This is happening because the server speaks HTTP3, and we have a hard-coded timeout of 30s there[1]. You can see that the request to e.g. /31 succeeds if you fetch in parallel another path e.g. /12 - because the response after 12s resets the idle timer. /12 of course is not sufficient if the longer-waiting resource is greater than 12+30=42. MT says this shouldn't be hard to make configurable, but I'm not sure whether the right option here is to do that, or to just make it clear that the http connection-timeout pref doesn't apply to H3.
Bug 1719658 Comment 2 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
This is happening because the server speaks HTTP3, and we have a hard-coded timeout of 30s there[1]. You can see that the request to e.g. /31 succeeds if you fetch in parallel another path e.g. /12 - because the response after 12s resets the idle timer. /12 of course is not sufficient if the longer-waiting resource is greater than 12+30=42. Disabling HTTP3 also results in success. MT says this shouldn't be hard to make configurable, but I'm not sure whether the right option here is to do that, or to just make it clear that the http connection-timeout pref doesn't apply to H3. [1] https://github.com/mozilla/neqo/blob/0e8279fb4a4dd665401e144c81f04aa27965973b/neqo-transport/src/connection/idle.rs#L10