Sorry, I may not have been too clear:
A) I'm not trying to cache https
B) I'm not trying to transproxy https
The problem, when manually configuring to proxy https, is apparently
with the content of the request upon reaching the secure server. This
problem appears to exist as a result of some problem with squid or my
squid.conf. It could be an apache problem but note that it works when
using my parent squid directly.
So, whilst taking into account A) and B) above, it still don't work for
me ;-)
Regards,
Jeffrey Borg wrote:
>
> Simple answer to this question is
>
> A) squid only acts as a proxy for https, it carn't cache anything
> sent over https (that's the idea of it, to stop evesdropping on
> connections) only the client (web browser) and server know what's going
> on.
>
> B) there is no point in transparently proxing https connections
>
> if you are transparently proxing http then it's fine don't bother with
> https one bit, if you set the https proxy to your squid box then it will
> work fine squid just acts as a plain proxy.
>
> Jeff
-- ---------------------------------------------------------------------- Alastair Waddell o Tel +61 3 96400400 Legion Internet Queen Street, Melbourne o Full featured VISP Facility Virtual Services + DNS Maintenance + ISP Co-location + InternetworkingReceived on Sun Dec 13 1998 - 03:57:21 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:43:38 MST