-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16/02/2015 3:38 p.m., James Beecham wrote:
> Hi Amos,
>
> Thank you for your reply.
>
> The information I need to apply to the header is client specific,
> ex their internal ip address.
>
> The issue I am facing is that the network that is hostin
Hi Amos,
Thank you for your reply.
The information I need to apply to the header is client specific, ex their
internal ip address.
The issue I am facing is that the network that is hosting the web services
is different from the network that the clients are accessing it from. So my
Squid instance
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16/02/2015 11:46 a.m., Yuri Voinov wrote:
>
>
> 16.02.15 4:40, James Beecham пишет:
>> Hi Yuri,
>
>> Thank you.
>
>> Are these HTTPS CONNECT requests coming over port 80? If not
>> would I need
>
> It depends. In different configurations uses d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
16.02.15 4:40, James Beecham пишет:
> Hi Yuri,
>
> Thank you.
>
> Are these HTTPS CONNECT requests coming over port 80? If not would
> I need
It depends. In different configurations uses different ports. In
transparent interception mode your absol
Hi Yuri,
Thank you.
Are these HTTPS CONNECT requests coming over port 80? If not would I need
to make a rule to forward 443 to another Squid port configured to ssl_bump?
James
On Sun, Feb 15, 2015 at 2:37 PM, Yuri Voinov wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> http://wiki
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
http://wiki.squid-cache.org/ConfigExamples/Intercept/SslBumpExplicit
16.02.15 4:02, James Beecham пишет:
> Hello,
>
> Thank you to everyone who works on this great project! I have been
> using Squid as an intercept for a while now and am very happy.
Hello,
Thank you to everyone who works on this great project! I have been using
Squid as an intercept for a while now and am very happy.
I have a high level question regarding SSL_Bump.
My company recently switched to using SSL for our web services, which
requires me to make some changes to the
