We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Thank you so much for httparse all your other amazing libraries.
httparse
Sorry for the maybe bad bug report, I am not a HTTP expert.
With the new 1.9 version I get a test regression in oxhttp with strange parsing result. A : gets included in one of the header value.
:
Here is a test to reproduce the possible regression:
#[test] fn test_http_parse() { let mut headers = [httparse::EMPTY_HEADER; 1024]; let mut parsed_request = httparse::Request::new(&mut headers); parsed_request .parse(b"POST / HTTP/1.1\ncontent-length:4\n\n") .unwrap(); for header in parsed_request.headers { if header.name == "content-length" { assert_eq!(header.value, b"4"); // Fails, we get ':4' } } }
Thank you again for your library.
The text was updated successfully, but these errors were encountered:
Thanks for the report, PR at #174.
Sorry, something went wrong.
Thank you!
Successfully merging a pull request may close this issue.
Thank you so much for
httparse
all your other amazing libraries.Sorry for the maybe bad bug report, I am not a HTTP expert.
With the new 1.9 version I get a test regression in oxhttp with strange parsing result. A
:
gets included in one of the header value.Here is a test to reproduce the possible regression:
Thank you again for your library.
The text was updated successfully, but these errors were encountered: