header
Sent by:"squid-users"
On Friday 12 June 2015 at 16:08:59 (EU time), Julianne Bielski wrote:
> reverse proxies are always "transparent" from the perspective of
> the client and the Host header is often used by the proxy
> to map to the correct back end
I have a general question about the use of the http Host request header by
reverse proxies.
As I understand it, the Host request header is used by transparent forward
proxies as a way to route a request to the correct
origin server since, unlike with an explicit proxy, the host is not
included in
Amos,
Per:
There *is* a Right Way.
It is this:
1) using this in squid.conf:
https_port 3129 cert=/path/to/proxy.pem
2) client connects to 3129 using TCP, then performs TLS handshake.
3) client sends requests inside the encrypted connection as if they were
HTTP to a proxy but using https:
v
To: Julianne Bielski/Raleigh/IBM@IBMUS
Cc: squid-users@lists.squid-cache.org, squid-users
Date: 03/01/2015 12:52 PM
Subject:Re: [squid-users] question about encrypted connection between
https client and Squid
-BEGIN PGP SIGNED MESSAGE-
Hash:
and Squid
Sent by:"squid-users"
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
01.03.15 23:18, Julianne Bielski пишет:
>
> I have an https client (not a browser) that normally connects to a
> reverse proxy. When it needs to go through a forward proxy, it
> requests a CONNECT
I have an https client (not a browser) that normally connects to a reverse
proxy. When it needs to go through a forward proxy, it requests a CONNECT
tunnel.
I now have a requirement to also be able to encrypt the connection between
my client and the forward proxy, and I think this is possible usin
