Re: [squid-users] Possible to user reply_header_add directive with acl random access list ?

Hi Alex, acl half1 random 1/10 acl half10001 random 1/9 acl half10002 random 1/8 acl half10003 random 1/7 acl half10004 random 1/6 acl half10005 random 1/5 acl half10006 random 1/4 acl half10007 random 1/3 acl half10008 random 1/2 acl half10009 random 1/1 ##

Re: [squid-users] sending certificate chain from squid reverse proxy

On 17/07/19 12:34 am, Kate Dawson wrote: > Hi, > > Is it possible to send a certificate chain from squid when it's used in > reverse proxy (accel) mode and compiled with gnutls ? > That has not been implemented yet. Sorry. > > is it possible to send an intermediate certificate when build wi

Re: [squid-users] Possible to user reply_header_add directive with acl random access list ?

On 17/07/19 9:41 pm, --Ahmad-- wrote: > Hi Alex, > acl half1 random 1/10 > acl half10001 random 1/9 > acl half10002 random 1/8 > acl half10003 random 1/7 > acl half10004 random 1/6 > acl half10005 random 1/5 > acl half10006 random 1/4 > acl half10007 random 1/3 > acl half10008 random 1/2 > acl

Re: [squid-users] Possible to user reply_header_add directive with acl random access list ?

Hi Amos , Thank you for you info . indeed i read about reply header ACL That : ## One or more Squid ACLs may be specified to restrict header injection to matching responses. As always in squid.conf, all ACLs in the ACL list must be satis

Re: [squid-users] Possible to user reply_header_add directive with acl random access list ?

On 7/17/19 7:55 AM, --Ahmad-- wrote: > indeed i read about reply header ACL That : > all ACLs in > the ACL list must be satisfied for the insertion to happen. Amos is right, but the documentation you quote has nothing to do with the fact that each reply_header_add rule is checked. That arguably

Re: [squid-users] SOLVED - SECURITY ALERT: Host header forgery detected

(old thread revived) A common problem is with sites that have very short TTLs. For instance login.live.com sometimes has a TTL of 60 seconds. The squid server is using BIND as a recursive DNS resolver and clients are using the same BIND instance too. All clients (iOS, Windows, Android) sometimes

Re: [squid-users] Possible to user reply_header_add directive with acl random access list ?

Thanks Alex , i tried your acl not recognised ! 2019/07/17 09:21:42| FATAL: Invalid ACL type ‘annotate_client' do i need to recompile squid to enable this kind of ACLS ? > On 17 Jul 2019, at 16:05, Alex Rousskov > wrote: > > markProcessed ___ s

Re: [squid-users] SOLVED - SECURITY ALERT: Host header forgery detected

On 7/17/19 10:20 AM, Stephen Borrill wrote: > A common problem is with sites that have very short TTLs. > > For instance login.live.com sometimes has a TTL of 60 seconds. The squid > server is using BIND as a recursive DNS resolver and clients are using > the same BIND instance too. All clients (

Re: [squid-users] Possible to user reply_header_add directive with acl random access list ?

On 7/17/19 10:40 AM, --Ahmad-- wrote: > 2019/07/17 09:21:42| FATAL: Invalid ACL type ‘annotate_client' > do i need to recompile squid to enable this kind of ACLS ? These ACLs are only supported in the development version of Squid (future v5): https://github.com/squid-cache/squid/commit/63e82d8

Re: [squid-users] Possible to user reply_header_add directive with acl random access list ?

Hi Alex thanks for info . well have compiled squid 5 and i made exact steps as you mentioned . now i have delayed responce with single header info . but its wrong value . not correct reply header !!! so instead of getting START A i see START B or E and so on . > On 17 Jul 2019, at 1