You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 13, 2021. It is now read-only.
(Related to #314, but impacts the request side of things)
Because of the way HTTPHeaderMap splits header values on commas into multiple ways, servers may have trouble understanding headers with multiple values.
Example:
This is a minimal example, but I have run into situations where the server (outside of our control) expects the headers to be in a very specific format.
The text was updated successfully, but these errors were encountered:
Agreed, this is unacceptable. A more common scenario is using the User-Agent header (since a lot of servers will perform filtering on this header), and getting your requests denied because they don't know how to deal with multiple headers with the same key.
For anyone looking for a quick fix, you can perform this monkey patch:
(Related to #314, but impacts the request side of things)
Because of the way HTTPHeaderMap splits header values on commas into multiple ways, servers may have trouble understanding headers with multiple values.
Example:
Output:
Expected output (note the spaces in Accept-Encoding):
The following curl command retrieves the expected output:
This is a minimal example, but I have run into situations where the server (outside of our control) expects the headers to be in a very specific format.
The text was updated successfully, but these errors were encountered: