-
Notifications
You must be signed in to change notification settings - Fork 427
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
invalid_proxy_transport - returned with https proxy requesting https host #705
Comments
@canuc pleas eprovide more detail, any snippet I could look at ? |
please provide more info there about the issue. https proxies should work.
|
The client rejects any requests where both the proxy scheme and the end request scheme are https. See here: Line 629 in d6d075f
|
@benoitc Why was my previous comment deleted? Did it not follow the community guidelines? I'm sorry if that was the case. |
what specification it is ? to my knowlwdge proxying https to httpta was not
specified.
Le lun. 24 avr. 2023 à 17:23, João Bernardo ***@***.***> a
écrit :
The client rejects any requests where both the proxy scheme and the end
request scheme are https.
See here:
https://github.com/benoitc/hackney/blob/d6d075f9edcbb7e0b5c9418dba5dd34f2c95bc21/src/hackney.erl#L629
—
Reply to this email directly, view it on GitHub
<#705 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAADRIQCGNVJTACDBVA56WDXC2LHRANCNFSM5VSGGHUQ>
.
You are receiving this because you were assigned.Message ID:
***@***.***>
--
Sent from my Mobile
|
As far as I'm aware there isn't a specification for it, it's a variation of the classic HTTP proxying where the connection between the client and the proxy is over TLS instead. |
ok i will find an api for it. i think this require separate cerificates to
work. there is a new version landing on thursday. will try to add it.
Le lun. 24 avr. 2023 à 17:31, João Bernardo ***@***.***> a
écrit :
As far as I'm aware there isn't a specification for it, it's a variation
of the classic HTTP proxying where the connection between the client and
the proxy is over TLS instead.
—
Reply to this email directly, view it on GitHub
<#705 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAADRIXDD6O66C6DIX75ST3XC2MFRANCNFSM5VSGGHUQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Sent from my Mobile
|
Noticed that if the proxy transport is https and the end transport is https -> the request will return invalid_proxy_transport. This seems like https proxies are not supported or am I missing something?
The text was updated successfully, but these errors were encountered: