Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Validate pseudo-headers in requests/responses #13646

Open
isaacrivriv opened this issue Oct 3, 2023 · 0 comments · May be fixed by #13647
Open

Validate pseudo-headers in requests/responses #13646

isaacrivriv opened this issue Oct 3, 2023 · 0 comments · May be fixed by #13647

Comments

@isaacrivriv
Copy link
Contributor 

          The (old) RFC 7540 has:

Pseudo-header fields defined for requests MUST NOT appear
in responses; pseudo-header fields defined for responses MUST NOT
appear in requests. Pseudo-header fields MUST NOT appear in
trailers.

Where are we doing that first part? I'd expect to see the mirror of this logic elsewhere. Do we just not have that logic anywhere?

Originally posted by @ejona86 in #13603 (review)

Need to validate Netty's behavior on this and if appropriate work on a fix to validate
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add validation for pseudo-headers on requests/responses isaacrivriv/netty
1 participant
@isaacrivriv