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

Bug with some proxies when using reqwest (reqwest is based on http underhood) #535

Closed
chirok11 opened this issue Mar 27, 2022 · 1 comment

Comments

@chirok11
Copy link

chirok11 commented Mar 27, 2022

Hello.
I have reached some HTTP proxies with authorization, which require http header names written as it's written in RFC.
when I am sending request by netcat

`GET http://site/ HTTP/1.1
proxy-authorization: Basic abcdef==
User-Agent: curl/7.79.1
Accept: /
Proxy-Connection: Keep-Alive

HTTP/1.1 504 Gateway Timeout
Date: Sun, 27 Mar 2022 10:17:59 GMT
Content-Type: text/plain; charset=utf-8
X-Content-Type-Options: nosniff
Connection: close`

but if I'll type capitalized ("Proxy-Authorization") as it wrote in RFC, then it will work without 504 gateway timeout error.
So question is - maybe you should rewrite name.rs file and replace all names with correct names from RFC?
I know that headers is case-insensitive, but it's normal practice to capitalize each word.

@seanmonstar
Copy link
Member

This has been discussed several times before, see #228 (comment) for the current thinking.

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

No branches or pull requests

2 participants