[squid-users] peer_cache / https Question

From: Michael Arndt <michael.arndt_at_berlin.de>
Date: Thu, 28 Apr 2011 12:06:32 +0200 (CEST)

Hello *,

For WLAN Clients ( untrusted ), i need to set up a 2nd squid proxy, since those clients are not able / allowed
to connect to the main proxy directly( local 172.168.x.x Network for WLAN ).

-works well with http, but https target URLS do not work ( server not reacheable )

Setup: WLANClient--->[Squid A on Server A]--->[Squid B on Server B]--->[Internet]

a) when i point an browser who has access to intranet directly to the upstream proxy squid B ist works, https
     requests are served

b) when i point my browser to Squid A

-http Requests work
-https Requests do not

Config wrt cache_peer:

cache_peer proxy.institute.de parent 8080 0 no-query default
...
never_direct allow all

proxy.institute.de is Squid B above and works ok for http / https when accessed directly

I also have configured CONNECT Method
acl CONNECT method CONNECT
and
http_access allow CONNECT SSL_ports

did i miss or missunderstand / misuse any of the above options ?
Server A has an explicit route to server B
I do not know if i would need an "explicit" backward route B -->A, both servers are able to communicate, so
routing seems to be ok

Goal is, to connect the WLAN Clients over staged proxy to Internet and enable access to https / http-URLS

TIA
Micha
Received on Thu Apr 28 2011 - 10:06:45 MDT

This archive was generated by hypermail 2.2.0 : Thu Apr 28 2011 - 12:00:03 MDT