-
Notifications
You must be signed in to change notification settings - Fork 430
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
hackney doesn't work with proxies configured to accept GET (no CONNECT) requests #76
Comments
And it is quite strange that hackney supports the same options proxy/proxy_auth as httpc without supporting |
@qrilka not sure it's strange.... Probably just forgot that header existed. Anyway I just setup different proxy there and will try to reproduce along the day. Thanks for the feedback :) |
@benoitc actually I was thinking about switching from httpc to hackney and they have quite similar API but somwhat different behaviour, and that was somewhat suprising for me. |
Thanks, but it's not a header - it's a different proxy connection method (using |
On Tue, Feb 11, 2014 at 10:17 AM, Kirill Zaborsky
yup i'ts not only the header. I am testing what could be done right now :)
|
At the moment hackney always makes CONNECT request when working through proxy. In fact, most proxies that can be found on Internet don't accept CONNECT, they work with GET only. For CONNECT they reply "403 forbidden". http://en.wikipedia.org/wiki/HTTP_tunnel - "HTTP Tunneling without using CONNECT" section.
For example 202.107.222.50:80 (not sure if it will work at the time when you read this issue though) works fine when set in browser but returns 403 when used in hackney:request. Difference in connection method can be seen in Wireshark.
It would be nice to add an option to use such proxies and have a way to specify which method should be used - CONNECT or GET.
The text was updated successfully, but these errors were encountered: