I have a http proxy and I also have an IM APP which only support connect via socks5 proxy, I search for privoxy but it only support convert socks proxy into http proxy, so what can I do?
Related
Our environment requires that all requests to the public internet go through a proxy that uses HTTP tunneling (HTTP Connect). I have a service from a vendor that is not able to use an HTTP Connect proxy.
My plan is to set up a transparent proxy that the service can send traffic to, which will redirect traffic to the HTTP Connect proxy.
service -> transparent proxy -> http connect proxy -> public internet
Is it possible to redirect this traffic without decrypting and re-encrypting the HTTPS request? I won't be able to install any custom certs on the initial service to allow this (and I don't want to view the contents of the HTTP messages anyway). Also, are there any proxies that are made specifically to do this, or will I need to write my own?
I am trying to redirect all traffic from localhost with a specific port to a socks5 proxy which has authentication. Kind of like how the Tor proxy works.
I tried usinc ncat, but it does not support socks5 proxies
It seems like quic-go does not support proxy for HTTP request like HTTP/2 module, how can I use HTTP/S proxy or SOCKS5 proxy with quic-go for HTTP requests?
The quic-go package doesn't seem to have native proxy support (it does have a class called proxy, but it appears to be a tool for testing packet loss and delays).
How about extending it yourself (or dynamically wrapping it) with net/proxy and then using this to forward your requests through a SOCKS5 proxy?
If I enter a SOCKS proxy into the http section of firefox proxy settings, it doesn't work, only with a http proxy. Shouldn't socks work for this, they're both proxies?
Is there any different between HTTP tunnel and HTTP proxy?
In some software I see two fields for proxy either HTTP and HTTP tunnel.
I see the traffic of some http proxy but I cant understand the different between http proxy and http tunnel.
The terms are often intermixed, tunnel providers are called proxies.
Originally, tunneling is the technique of using one protocol to transport data inside another protocol.
A proxy (as in proxy representative)
A proxy acts as an intermediary. It will hide your IP address from the destination (unless it adds it in a HTTP header field such as "Forward"). A proxy uses the same protocol throughout, it can alter the network flow, do caching or security scanning etc. So it's more of an extra hop on the way to the destination.
For example you can use a SOCKS proxy as a HTTP tunnel, i.e. you transport HTTP over it. This is due to the fact that SOCKS is a protocol that is designed to tunnel IP packets.
To add to the confusion, you can use a HTTP proxy to transport some other protocols such as FTP.
A good example for a tunnel is a VPN. Tunnels are often used to evade censorship or firewall rules blocking traffic.