[squid-users] External ACL with an HTTP reply header format doesn't

Hi, First of all my setup information Distribution: CentOS Linux release 7.0.1406 (Core) Kernel Version: Linux 3.10.0-123.8.1.el7.x86_64 x86_64 RPM Package Version: squid-3.3.8-12.el7_0.x86_64 Squid Cache: Version 3.3.8 configure options: '--build=x86_64-redhat-linux-gnu' '--host=x86_64-redhat-li

Re: [squid-users] squid basic ntlm auth error after upgrade to 3.3.8

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 21/11/2014 12:38 a.m., Lupick wrote: > Hi I've a problem authenticating users outside my AD domain after > the upgrade to squid 3.3.8. 3.3.8 is far from the latest Squid. There is information about where to find updated packages for CentOS at

Re: [squid-users] Problem with digest authentification and credential backend

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 20/11/2014 4:21 a.m., wmunny william wrote: > Hi, After some strange authentication issues, I saw that my problem > occurs when a admin sets a new password or removes a user. The > backend authentification is only checked in logon at first popup, >

Re: [squid-users] Pull/Fetch high level URL requests from Squid access.log without getting all the object hits

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 21/11/2014 3:31 a.m., Swapneel Patnekar wrote: > Dear Amos, > > Thank you for your input. > > The reason I had this requirement is to build a analytics app on > top of Squid which will only show typed URL's so that the end user > has the precise i

Re: [squid-users] probs with squid and url forwarding

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 21/11/2014 12:43 a.m., Andreas.Reschke wrote: >> Von: Amos Jeffries > On 20/11/2014 10:57 p.m., Andreas.Reschke wrote: Hi there, we're using 3 squid proxy (version 3.3.-13, no caching, no logging) at our LAN (4500 User) in fron

Re: [squid-users] Pull/Fetch high level URL requests from Squid access.log without getting all the object hits

Dear Amos, Thank you for your input. The reason I had this requirement is to build a analytics app on top of Squid which will only show typed URL's so that the end user has the precise information w.r.t evaluating web access. Currently, since everything gets logged into the access.log, there is

Re: [squid-users] Pull/Fetch high level URL requests from Squid access.log without getting all the object hits

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 21/11/2014 1:18 a.m., Swapneel Patnekar wrote: > Hi there, > > I need to pull/fetch high level URL requests from the Squid > access.log i.e URL requests which were typed by the user in the > browser. > > For example, if the user had typed facebook

Re: [squid-users] Pull/Fetch high level URL requests from Squid access.log without getting all the object hits

Hi, i think this cannot be done. In squid, we have option for custom log format, but in that also request for .css or .js or img will be logged. We cannot specifically log only the user typed url in the acces log. - Siva Prakash On 11/20/2014 05:48 PM, Swapneel Patnekar wrote: Hi there, I n

[squid-users] Pull/Fetch high level URL requests from Squid access.log without getting all the object hits

Hi there, I need to pull/fetch high level URL requests from the Squid access.log i.e URL requests which were typed by the user in the browser. For example, if the user had typed facebook.com, I want to pull/fetch only facebook.com from the access.log and not https://fbstatic-a.akamaihd.net/rsrc.p

[squid-users] squid basic ntlm auth error after upgrade to 3.3.8

Hi I've a problem authenticating users outside my AD domain after the upgrade to squid 3.3.8. All the domain logged user are able to authenticate without any issue. The local user or user of a non domain computer have a username/password prompt as expected. If I provide the right doamin\userna

Re: [squid-users] probs with squid and url forwarding

"squid-users" schrieb am 20.11.2014 11:07:57: > Von: Amos Jeffries > An: squid-users@lists.squid-cache.org > Datum: 20.11.2014 11:08 > Betreff: Re: [squid-users] probs with squid and url forwarding > Gesendet von: "squid-users" > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 20/11

Re: [squid-users] Assertion failure: DestinationIp.cc:60

On 19/11/14 05:29, Amos Jeffries wrote: > What is your config? In particular anything using ACLs. auth_param basic program /usr/lib64/squid/basic_pam_auth -r auth_param basic children 50 auth_param basic realm Iceni Web Proxy auth_param basic credentialsttl 2 hours workers 4 shutdown_lifetime 3

Re: [squid-users] RFC2616 headers in bumped requests

On 17/11/14 22:05, Amos Jeffries wrote: > Would you mind running an experiment for me? > > To see what happens if Squid delivers either of these Via headers > instead of its current output: > > Via: HTTPS/1.1 iceni2.opendium.net (squid/3.4.9) The HTTPS/1.1 one appears to work correctly. >

Re: [squid-users] probs with squid and url forwarding

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 20/11/2014 10:57 p.m., Andreas.Reschke wrote: > Hi there, > > we're using 3 squid proxy (version 3.3.-13, no caching, no > logging) at our LAN (4500 User) in front of a squid proxy at the > DMZ. Now there are a lot of troubles with portals for the

[squid-users] probs with squid and url forwarding

Hi there, we're using 3 squid proxy (version 3.3.-13, no caching, no logging) at our LAN (4500 User) in front of a squid proxy at the DMZ. Now there are a lot of troubles with portals for the costumer (like www.covisint.com). After register at this portal and select the application there is a f