On 24/11/15 18:26, Amos Jeffries wrote:
That is two separate and entirely different traffic types:
A) [client] -> HTTP--(NAT)--> [my_proxy]
B) [client] -> TLS--(NAT)--> [my_proxy]
(A) requires "http_port ... intercept ssl-bump cert=/path/to/cert"
(B) requires "https_port ... intercept
Hi Amos
On 09/11/15 12:55, Amos Jeffries wrote:
On 9/11/2015 11:55 a.m., Michael Ludvig wrote:
[client] -> HTTPS -> [my_proxy] -> SSL -> [upstream_proxy] -> HTTPS ->
[target]
Can you provide some config hints for both proxies please? The
SSL-related bits only as that'
Hi again
Does anyone have any idea how to fix the below described problem? Please :)
Thanks!
Michael
On 05/11/15 16:01, Michael Ludvig wrote:
Hi
I've got a network without direct internet access where I have Squid
3.5.9as a transparent proxylistening on tcp/8080for HTTP and on
tcp/8443for
Hi
I've got a network without direct internet access where I have Squid
3.5.9as a transparent proxylistening on tcp/8080for HTTP and on
tcp/8443for HTTPS (redirected via iptablesfrom tcp/80 and tcp/443
respectively).
This Squid (proxy-test) doesn't have a direct Internet access either but
