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.

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

feat(http1): add option allowng leading whitespaces before first header #3643

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dswij
Copy link
Member

@dswij dswij commented Apr 22, 2024

closes #3285

@hjr3
Copy link
Contributor

hjr3 commented Apr 27, 2024

This appears to be blocked on:

@dswij
Copy link
Member Author

dswij commented Apr 27, 2024

Yes. This PR is waiting for a new release of httparse to include the httparse changes you mentioned.

@seanmonstar
Copy link
Member

There was an httpparse v1.9 release that you can refer to, now.

@seanmonstar seanmonstar added the S-waiting-on-author Status: waiting on the author to provide more info, or make changes. label Jun 25, 2024
@nox
Copy link
Contributor

nox commented Jul 10, 2024

Do browsers actually parse the header, or do they ignore that header line just like they do for other kinds of invalid header lines? There was already an option to ignore invalid header lines in httparse, did it not make httparse silently ignore those initial headers with leading whitespace?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-author Status: waiting on the author to provide more info, or make changes.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Option to allow leading whitespace in first HTTP/1 response header
4 participants