Subject: Re: [quicwg/base-drafts] HTTP error codes use inconsistent language (#2765)

From: Mike Bishop <[email-masked]>
Date: Wed, 28 Aug 2019 12:48:22 -0700

The different value-judgement terms are corrected by the flurry of settings PRs that @LPardue already did.  HTTP_FRAME_ERROR has replaced malformed, and UNEXPECTED_FRAME and WRONG_STREAM are reasonably descriptive (though see #2809, #2996).

We do still have some variation between HTTP_THING_DESCRIPTOR, HTTP_THING_ERROR, and HTTP_DESCRIPTOR_THING (e.g. HTTP_UNEXPECTED_FRAME versus HTTP_REQUEST_REJECTED) that might be worth reconciling.

Is it worth turning into HTTP_FRAME_UNEXPECTED?

-- 
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/issues/2765#issuecomment-525895473