On 26/05/2015 9:30 p.m., Lucas van Braam van Vloten wrote:
> Hi,
>
> Thanks for your extensive replies, it really boosts my understanding of
> Squid :-)
>
>> No, because Squid is only aware of two ways to send request - either a
>> connection going to the TMG, or a connection going out directly o
essages to the TMG and you see it working as the tunnel
> spans both hops and they are both blind to the HTTPS messages
themselves.
-Original Message-From: Amos Jeffries
To: Lucas van Braam van Vloten ,
squid-users@lists.squid-cache.org
Subject: Re: [squid-users] Proxy chain question
On 23/05/2015 1:49 a.m., Lucas van Braam van Vloten wrote:
> Hello,
>
> Thanks for your reply.
>
>> Any particular reason?
> Unfortunately this double setup is not my choice, our architects
> prescribe use of the TMG proxy as mandatory for all internet access from
> the internal network. No excep
o initiate a https connection,
and handle the certificate authentication, from the squid server itself.
Considering the updated diagram, do you think this can be done in Squid?
Thanks,
Lucas
-Original Message-From: Amos Jeffries
To: squid-users@lists.squid-cache.org
Subject: Re: [squid-
On 22/05/2015 4:58 a.m., Lucas van Braam van Vloten wrote:
> Hello list,
>
> In my network I have a Microsoft TMG proxy server for http(s) access to
> internet.
> This TMG server also serves as a reverse proxy to channel incoming
> traffic to a Squid reverse proxy in the internal network (yes, two
Hello list,
In my network I have a Microsoft TMG proxy server for http(s) access to
internet.
This TMG server also serves as a reverse proxy to channel incoming
traffic to a Squid reverse proxy in the internal network (yes, two
reverse proxies in a line)
This Squid server is currently configured
