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
I need to implement a proxy (client side) with Wangle. The proxy server is already there, which is a simple HTTP proxy - the client can CONNECT to it, and send the message via the tunnel.
So I already have a pipeline ready, which is able to communicate with the destination directly. Does anyone have good ideas how to extend the original pipeline to support proxy? (ie. the direct destination is fixed to be the proxy while each connection can be configured in advance for the actual destination. I have no idea how to CONNECT to the server and distinguish different connections based on the actual destination.)
Thanks in advance!
Zhenyu
The text was updated successfully, but these errors were encountered:
@zhenyu-zhou sorry for the late reply. Are you trying to use HTTP CONNECT from your client - in which case you would need to add support for parsing / reconnecting to a different upstream. You might be able to use the proxygen library for this.
Hello,
I need to implement a proxy (client side) with Wangle. The proxy server is already there, which is a simple HTTP proxy - the client can
CONNECT
to it, and send the message via the tunnel.So I already have a pipeline ready, which is able to communicate with the destination directly. Does anyone have good ideas how to extend the original pipeline to support proxy? (ie. the direct destination is fixed to be the proxy while each connection can be configured in advance for the actual destination. I have no idea how to
CONNECT
to the server and distinguish different connections based on the actual destination.)Thanks in advance!
Zhenyu
The text was updated successfully, but these errors were encountered: