[quicwg/base-drafts] all HTTP/3 protocol violations should lead to connection errors (#2510)

[Kazuho Oku <[e-mail]>]

In reply to https://github.com/quicwg/base-drafts/pull/2508#issuecomment-471151993:
> @kazuho, that's a good question. Previously, the philosophy has been that connection errors are ones which screw up the state so badly you can't trust the connection to proceed correctly. It's a reasonable, but not bulletproof, argument that a peer which doesn't obey the protocol has the same implication -- you can't trust the connection.
> 
> If you see other protocol violations which are stream-local errors, please file issues and we'll discuss.

I did a quick search for "stream error" and found a few that discusses about protocol violation. This PR changes "connection error."
You can view, comment on, or merge this pull request online at:

  https://github.com/quicwg/base-drafts/pull/2510

-- Commit Summary --

  * all protocol violations should lead to connection errors

-- File Changes --

    M draft-ietf-quic-http.md (14)

-- Patch Links --

https://github.com/quicwg/base-drafts/pull/2510.patch
https://github.com/quicwg/base-drafts/pull/2510.diff

-- 
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/2510