On 07/08/18 16:28, Hariharan Sethuraman wrote:
> I found that login=PASS in cache_peer directive helped.
>
Indeed. cache_peer controls what Squid sends to that particular peer server.
>
> On Mon, Aug 6, 2018 at 11:29 PM, Hariharan Sethuraman wrote:
>
> I tried allow_direct as well as defau
I found that login=PASS in cache_peer directive helped.
Thanks,
Hari
On Mon, Aug 6, 2018 at 11:29 PM, Hariharan Sethuraman
wrote:
> I tried allow_direct as well as defaultsite under accel.
> Wondering if I should recompile squid with enable-http-violation and use
> below ACL /
>
> request_heade
I tried allow_direct as well as defaultsite under accel.
Wondering if I should recompile squid with enable-http-violation and use
below ACL /
request_header_access Authorization deny all
On Mon, Aug 6, 2018 at 11:23 PM, Matus UHLAR - fantomas
wrote:
> On 06.08.18 23:14, Hariharan Sethuraman w
On 06.08.18 23:14, Hariharan Sethuraman wrote:
I have my squid as reverse proxy (without any auth) between my client and a
web server. My HTTP request from client has an Authorization in its HTTP
header which I wanted it to be forwarded to target server. But from
cache.log I see squid is droppin
On 06.08.18 23:14, Hariharan Sethuraman wrote:
I have my squid as reverse proxy (without any auth) between my client and a
web server. My HTTP request from client has an Authorization in its HTTP
header which I wanted it to be forwarded to target server. But from
cache.log I see squid is droppin
