On 19/08/2016 10:42 p.m., Torsten Kuehn wrote:
> Hi,
>
> On 18/08/2016 6:32 a.m., Amos Jeffries wrote:
>
>>> I imagine layouts where the encrypted traffic itself gets stored
>> no way for Squid to know if a previous encrypted stream is reusable.
>> To squid it is just a random stream of opaque by
Hi,
On 18/08/2016 6:32 a.m., Amos Jeffries wrote:
>> I imagine layouts where the encrypted traffic itself gets stored
> no way for Squid to know if a previous encrypted stream is reusable.
> To squid it is just a random stream of opaque bytes.
Enlightening! The idea was that omitting decryption
On 18/08/2016 11:00 a.m., Torsten Kuehn wrote:
> Thank you for your quick reply!
>
> On 17/08/2016 6:01 p.m., Amos Jeffries wrote:
>
>>> I am forced to stuck with 2.X
>> Then you cannot decrypt the HTTPS in order to cache it. Squid older than
>> 3.2 simply do not have any of the functionality to
Thank you for your quick reply!
On 17/08/2016 6:01 p.m., Amos Jeffries wrote:
>> I am forced to stuck with 2.X
> Then you cannot decrypt the HTTPS in order to cache it. Squid older than
> 3.2 simply do not have any of the functionality to do so.
I.e. not cacheable at all? May sound stupid but I
On 18/08/2016 3:23 a.m., Torsten Kühn wrote:
> Dear Mailing List,
>
> older Squid versions have been obsoleted by 3.X and 4.X, I (barely)
> dare to ask a 2.X-related question ... For particular reasons, I am
> forced to stuck with 2.X
Then you cannot decrypt the HTTPS in order to cache it. Squid
Dear Mailing List,
older Squid versions have been obsoleted by 3.X and 4.X, I (barely)
dare to ask a 2.X-related question ... For particular reasons, I am
forced to stuck with 2.X: my cache contains objects since 2010, of
personal value. Due to small bandwith (ISDN speed), I use Squid
as a "buffer
