| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Signed-off-by: harjoth <harjoth.khara@gmail.com>
|
Review requested:
|
Sorry, something went wrong.
Signed-off-by: harjoth <harjoth.khara@gmail.com> PR-URL: #64548 Reviewed-By: Aviv Keller <me@aviv.sh> Reviewed-By: James M Snell <jasnell@gmail.com>
Signed-off-by: harjoth <harjoth.khara@gmail.com> PR-URL: #64548 Reviewed-By: Aviv Keller <me@aviv.sh> Reviewed-By: James M Snell <jasnell@gmail.com>
| Back | FazBrowse Home | New Git URL |
Summary
Closes #25952.
Related: #64235, which was closed unmerged after addressing the compatibility
example and leaving the constants documentation for a follow-up.
This change:
interchangeable with accepted literal header names;
validation, trailers, and connection-specific fields;
are set directly through writeHead().
The documentation is the correct fix boundary because the runtime constants
and behavior already exist. This change does not alter HTTP/2 runtime behavior,
public APIs, or compatibility. The blast radius is limited to
doc/api/http2.md.
Verification
The full documentation target passed:
The existing HTTP/2 binding test passed:
All documented constant names and values were compared with the current
runtime export:
The committed diff also passes:
Real-behavior proof
This uses an actual HTTP/2 compatibility server and client. It compares a
response using HTTP2_HEADER_CONTENT_TYPE with one using the mixed-case
literal Content-Type, verifies the client-visible status, headers, and body,
and checks compatibility-API rejection of HTTP2_HEADER_STATUS.
AI-assisted: developed with OpenAI Codex; I reviewed the documentation and verified the behavior and test results above.