Hi,
I am setting up a transparent proxy that is doing whitelist work, and at
the same time, doing the cache work.
The whitelist works fine, HTTP cache verifed work cause I see TCP_MEM_HIT
using this squid.conf, but don't see any HTTPS MEM HIT related log, every
time seems a new connection.
F
3131 proxy-only
Thanks,
Lei
On Tue, Jul 25, 2017 at 9:42 PM, Amos Jeffries wrote:
> On 26/07/17 10:56, Lei Wen wrote:
>
>> Hi,
>>
>> I am setting up a transparent proxy that is doing whitelist work, and at
>> the same time, doing the cache work.
>>
>&g
t are doing similar job, so they can share
cache between different hosts. This is our initial idea for this project if
you know there are better hierarchy and can give me some suggest I am
really appreciate.
Thanks,
Lei
On Wed, Jul 26, 2017 at 3:30 PM, Amos Jeffries wrote:
> On 27/07/1
ies wrote:
> On 28/07/17 10:32, Lei Wen wrote:
>
>> Hi Amos,
>>
>> /Squid does not support relaying decrypted https:// requests over an
>> insecure connection. So HTTP cache_peer connections will be refused./
>>
>> Do you mean HTTPS cache_peer connect
Hi,
I am setting up the transparent HTTP/HTTPS proxy cluster with whiltelist
only, and stuck at having issue 'ERROR 500: Internal Server Error'. After
couple days tuning and digging, I narrow down the problem to directive
'never_direct'.
After removing this line, the error message is gone. But se
I am using request_header_replace to modify out going HTTP headers, mainly
the basic/bearer token. Does request_header_replace support calling another
file, the content in that file would be "Basic ...".
Thanks,
Lei
___
squid-users mailing list
squid
Hi,
We were able to set up the squid in a host to container infrastructure.
That is saying the squid is installed on host, proxying traffic from the
container on the same host. With transparent proxy including SSL traffic.
Another feature we enabled is request_header_access and
request_header_r