Re: [squid-users] icap result caching in squid

2019-12-05 Thread Darren Breeze
nks again. Darren B. On Wed, Dec 4, 2019, at 6:26 PM, Amos Jeffries wrote: > On 4/12/19 6:05 am, Darren Breeze wrote: > > Hi Amos > > > > The Icap service is doing redirects based on client permissions (that may > > change). What I am doing is just setting the Expir

Re: [squid-users] icap result caching in squid

2019-12-04 Thread Darren Breeze
want to do so it makes my intent clearer to others reading the code in the future. Thanks again. Darren B. On Wed, Dec 4, 2019, at 6:26 PM, Amos Jeffries wrote: > On 4/12/19 6:05 am, Darren Breeze wrote: > > Hi Amos > > > > The Icap service is doing redirects based on cl

Re: [squid-users] icap result caching in squid

2019-12-03 Thread Darren Breeze
. On Tue, Dec 3, 2019, at 6:17 PM, Amos Jeffries wrote: > On 3/12/19 12:17 pm, Darren Breeze wrote: > > Thanks Alex. > > > > That has given me the perspective I need. > > > > I can modulate the response header Expires value via icap to get the job > > done whe

Re: [squid-users] icap result caching in squid

2019-12-02 Thread Darren Breeze
Thanks Alex. That has given me the perspective I need. I can modulate the response header Expires value via icap to get the job done when squid goes to cache it. Darren B. *Darren Breeze* Director *KSN Systems NZ Limited* **E: *dar...@ksn-systems.com* **M:* +64 274 666 017* **S:* dbinhk* On

[squid-users] icap result caching in squid

2019-11-29 Thread Darren Breeze
Hi all. Some quick question about icap result caching in squid. Does the returned Expires header control how long squid will cache the result (for both a req and resp mod)? Are the values that are cached keyed to the queried URL or is it cached per user / url? thanks Darren B. This em

Re: [squid-users] Header forgery detected

2019-11-09 Thread Darren Breeze
Thank You Amos There was a second DHCP service on that network handing out conflicting DNS data. Once that was stopped, everything worked as expected. Darren B. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom

[squid-users] Header forgery detected

2019-11-08 Thread Darren Breeze
Hi All I am trying to set up squid 3.5 (have to stick with this version) to intercept and https bump / splice, it's all working OK with the exception of some elements of a https site failing to load (the browser just shows "failed"). matched with the failures, I see this type of message in the

Re: [squid-users] Icap redirection issues

2019-10-10 Thread Darren Breeze
Hi Alex Thank you, I have removed that req header header and it is now redirecting thanks Darren B. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error ple

[squid-users] Icap redirection issues

2019-10-10 Thread Darren Breeze
HI I am trying to set up redirection via icap for a project I am working on. my current icap config looks like this icap_service service_res respmod_precache icap://127.0.0.1:1344/respmode bypass=0 adaptation_access service_res allow all and I am generating responses that look like this (in th

Re: [squid-users] 3.5.8 Arm7 socket permissions

2015-10-30 Thread Darren Breeze ML
68.192.46/ksn-100/linux-rockchip/commit/cfc6ca5f859517957c323c340d754338211dbc61>* and a rebuild has solved the issue. Thanks again Amos for prodding me along to the fix. Darren B. On 29/10/2015 8:00 PM, Amos Jeffries wrote: On 29/10/2015 11:11 p.m., Darren Breeze ML wrote: Hi Thanks f

Re: [squid-users] 3.5.8 Arm7 socket permissions

2015-10-29 Thread Darren Breeze ML
t the IP address. I am guessing now I may have missed something out of the kernel, but everything else seems to work, including Nginx on the same machine. thanks again Darren Breeze On 29/10/2015 8:00 PM, Amos Jeffries wrote: debug_options

Re: [squid-users] 3.5.8 Arm7 socket permissions

2015-10-29 Thread Darren Breeze ML
On 29/10/2015 11:16 a.m., Darren Breeze ML wrote: Hi all I have built squid 3.5.8 with yocto to run on an arm 7. This build of the OS seems to have different permissions for processes opening sockets. THe DNS routine fails to open a socket with the following error root@test:~# 2015/10/28 22:07:

[squid-users] 3.5.8 Arm7 socket permissions

2015-10-28 Thread Darren Breeze ML
Hi all I have built squid 3.5.8 with yocto to run on an arm 7. This build of the OS seems to have different permissions for processes opening sockets. THe DNS routine fails to open a socket with the following error root@test:~# 2015/10/28 22:07:43 testing| Starting Squid Cache version 3.5.8

[squid-users] SSL ACL issue on cross compile

2015-10-27 Thread Darren Breeze ML
ts/rk3188/usr/lib/pkgconfig:/home/darren/yockto/build/tmp/sysroots/rk3188/usr/share/pkgconfig''PKG_CONFIG_LIBDIR=/home/darren/yockto/build/tmp/sysroots/rk3188/usr/lib/pkgconfig' root@test:/opt/remote/scripts# squid 2015/09/09 04:02:03| ACL not found: ssl::certUn

[squid-users] Squid 3.5.8 cross compile SSL ACL issues

2015-10-26 Thread Darren Breeze ML
onfig''PKG_CONFIG_LIBDIR=/home/darren/yockto/build/tmp/sysroots/rk3188/usr/lib/pkgconfig' root@test:/opt/remote/scripts# squid 2015/09/09 04:02:03| ACL not found: ssl::certUntrusted FATAL: Bungled Default Configuration (postscriptum) line 1: sslproxy_cert_sign signUntrusted ss