Skip to content

Send correct requests & responses #22

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.

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

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

DemiMarie
Copy link

@DemiMarie DemiMarie commented Jun 11, 2025

Proposed changes

Only send well-formed messages to NGINX, unless a test is about non-conforming messages being rejected.

Checklist

Before creating a PR, run through this checklist and mark each as complete:

A check that NGINX accepts malformed HTTP/2 or HTTP/3 requests should
be specific to such malformed requests, not hidden in general tests for
HTTP/2 and HTTP/3 headers.
Do not use a regular expression that matches CR.
Lots of code used a bare LF in the HTTP protocol, but that is wrong:
RFC9112 is very clear that CRLF is the HTTP line terminator.

Most of the changes are just replacing \n with \r\n or adding missing \r
in heredocs, but it is also necessary to update byte counts to include
the extra bytes.
@DemiMarie DemiMarie changed the title DSend correct requests & responses Send correct requests & responses Jun 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant