-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Add support for multiline header in response #1521
Comments
Such "malformed" cookies are generated by a WAF for detection purposes. So there is a good reason to support it in the library. |
eyalsatori
added a commit
to eyalsatori/reqwest
that referenced
this issue
Apr 12, 2022
…ine_headers_in_responses (seanmonstar#1521)
eyalsatori
added a commit
to eyalsatori/reqwest
that referenced
this issue
Apr 19, 2022
…ine_headers_in_responses (seanmonstar#1521)
eyalsatori
added a commit
to eyalsatori/reqwest
that referenced
this issue
Apr 19, 2022
…ine_headers_in_responses (seanmonstar#1521)
Added in #1523 |
Nutomic
pushed a commit
to Nutomic/reqwest
that referenced
this issue
Nov 7, 2024
…ine_headers_in_responses (seanmonstar#1521) (seanmonstar#1523)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Following this discussion - I saw that the server send me a set-cookie header with multiline value (CLRF in the middle of the cookie).
this is print from curl output:
I saw that hyper support multiline header by configuration , and I thought maybe it's can be added also as ClientBuilder flag .
If you ok with this attitude , I will start to working on PR .. (I think it's should be pretty convenient - I will follow the path of http1_title_case_headers )
The text was updated successfully, but these errors were encountered: