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

Proxy-Authorization not returned #465

Open
aliowka opened this issue May 23, 2018 · 1 comment
Open

Proxy-Authorization not returned #465

aliowka opened this issue May 23, 2018 · 1 comment

Comments

@aliowka
Copy link

aliowka commented May 23, 2018

Looks like #251 is still there.

@javabrett
Copy link
Contributor

javabrett commented Jul 26, 2018

Does not reproduce on a current master branch local Docker container, but does on http://httpbin.org . My guess is that this is a hosting-feature from Vegur:

< HTTP/1.1 200 OK
< Connection: keep-alive
< Server: gunicorn/19.9.0
< Date: Thu, 26 Jul 2018 21:52:13 GMT
< Content-Type: application/json
< Content-Length: 537
< Access-Control-Allow-Origin: *
< Access-Control-Allow-Credentials: true
< Via: 1.1 vegur

https://github.com/heroku/vegur/blob/a2799234e1ae08beba22234ef0d106c94ddcdfa3/src/vegur_headers.erl#L110

delete_hop_by_hop([{<<"proxy-authorization">>, _} | Hdrs]) -> delete_hop_by_hop(Hdrs);

By the RFC I would expect this header to be consumed/dropped by an inbound proxy-chain.

Do you have a firm requirement for it? Maybe run a local instance?

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