Re: [squid-users] Squid 3.5.12

On 24/02/2016 10:05 a.m., nando mendonca wrote: > Could not Activate TLS connection I found this in the archives, might be useful for you: Amos ___ squid-users mailing list squid-u

Re: [squid-users] Squid 3.5.12

This is what i got: Could not Activate TLS connection On Tue, Feb 23, 2016 at 12:46 PM, Amos Jeffries wrote: > On 24/02/2016 9:10 a.m., Nando Mendonca wrote: > > Hi All, > > > > I had Squid 3.5.12 running with ldap authentication on port 389 great. > I now need to run squid on port 636. With

Re: [squid-users] Squid 3.5.12

On 24/02/2016 9:10 a.m., Nando Mendonca wrote: > Hi All, > > I had Squid 3.5.12 running with ldap authentication on port 389 great. I now > need to run squid on port 636. With my same configuation i'm unable to get > squid working. > > What compile options do i need? I was using basic_ldap_au

Re: [squid-users] Squid 3.5.12

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 This is not about compilation options. This about configuration, man. 24.02.16 2:10, Nando Mendonca пишет: > Hi All, > > I had Squid 3.5.12 running with ldap authentication on port 389 great. I now need to run squid on port 636. With my same con

[squid-users] Squid 3.5.12

Hi All, I had Squid 3.5.12 running with ldap authentication on port 389 great. I now need to run squid on port 636. With my same configuation i'm unable to get squid working. What compile options do i need? I was using basic_ldap_auth do i need to use something else? I can communicate from

Re: [squid-users] Squid 3.5.12 RPMs update for CentOS 7.

I have just updated the CentOS 7 build due to an error in the the build process of the RPM auto dependencies identification. Details: When the RED-HAT rpm build tools sets the dependencies for a script it sets the "shbang" binary location as a static dependency requirement. In this specific cas

Re: [squid-users] Squid 3.5.12 RPMs release for CentOS 6 and 7.

Thanks On 21 December 2015 at 21:57, Eliezer Croitoru wrote: > Published at: http://www1.ngtech.co.il/wpe/?p=166 > > I am happy to release the new RPMs of squid 3.5.12 for Centos 6 64bit, 32bit > and CentOS 7 64bit. > > The new release includes couple bug fixes and improvements. > I have also too

[squid-users] Squid 3.5.12 for Microsoft Windows 64-bit is available

Greetings everyone, The CygWin based build of Squid proxy for Microsoft Windows version 3.5.12 is now available (amd64 only!). * Original release notes are at http://www.squid-cache.org/Versions/v3/3.5/squid-3.5.12-RELEASENOTES.html. * Ready to use MSI package can be downloaded from http:/

[squid-users] Squid 3.5.12 RPMs release for CentOS 6 and 7.

Published at: http://www1.ngtech.co.il/wpe/?p=166 I am happy to release the new RPMs of squid 3.5.12 for Centos 6 64bit, 32bit and CentOS 7 64bit. The new release includes couple bug fixes and improvements. I have also took the time to build the latest beta 4.0.3 RPM for CentOS 7. The details

Re: [squid-users] squid 3.5.12 and ecap

Hi  thanks for you response. I compiled squid on debian jessie On Wednesday, December 16, 2015 6:38 AM, Amos Jeffries wrote: On 16/12/2015 12:53 a.m., behrad eslami wrote: > Hi I add simple rule to ecap module and deny some url. I forground > (squid -N -d10) all things work well. when

Re: [squid-users] squid 3.5.12 and ecap

On 16/12/2015 12:53 a.m., behrad eslami wrote: > Hi I add simple rule to ecap module and deny some url. I forground > (squid -N -d10) all things work well. when i run service wtih mutiple > workers, after a while some url not filter and user can open them in > browsers. I compile Squid 3.5.12 and l

[squid-users] squid 3.5.12 and ecap

Hi I add simple rule to ecap module and deny some url. I forground (squid -N -d10) all things work well. when i run service wtih mutiple workers, after a while some url not filter and user can open them in browsers. I compile Squid 3.5.12 and libecpa 1.0.0. squid compiled with below options:'--b