Re: [quicwg/base-drafts] [HTTP/3] [editorial] 421 and future connection reuse. (#3218)

[Mike Bishop <[e-mail]>]

>From 7540, as you quote, emphasis added:
> The 421 (Misdirected Request) status code indicates that the request was directed at a server that is not able to produce a response. **This can be sent by a server that is not configured to produce responses for the combination of scheme and authority that are included in the request URI.**

It's true that the definition of 421 doesn't call out client behavior for future requests, but the condition it describes would apply to an entire origin, so that's a logical implementation (and what I believe most user-agents do).

Is your suggestion that we not explicitly call out that behavior, or make it only illustrative?

>From RFC7838:
>    Clients receiving 421 (Misdirected Request) from an alternative service MUST remove the corresponding entry from its alternative service cache (see Section 2.2) for that origin.

Dealing specifically with alternatives, this requirement has the direct effect that you don't ask the alternate for any other resources from that origin, even though you still have a connection open to it.  In the current state of the draft, this has the effect of disabling HTTP/3 for that origin until you get a fresh Alt-Svc entry.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/3218#issuecomment-552609859