Re: [squid-users] compile error on Squid 3.1.18

Hi everybody, the problem related to ssl detection still stands in 3.1.18 branch. /usr/local/src/squid-3.1.18/src/ssl/gadgets.cc:110: undefined reference to `X509_set_issuer_name' /usr/local/src/squid-3.1.18/src/ssl/gadgets.cc:117: undefined reference to `X509_set_notAfter'

Re: [squid-users] compile error on Squid 3.1.18

Hi Jose, My problem (a link problem) was solved when I inverted the order of SSLLIB and SSL_LIBS inside src/Makefile squid/squid-3.1.18 diff src/Makefile.org src/Makefile 1893c1893 $(SSLLIB) $(SSL_LIBS) -lmiscutil $(EPOLL_LIBS) $(MINGW_LIBS) \ --- $(SSL_LIBS) $(SSLLIB) -lmiscutil

Re: [squid-users] Compiling squid-3.1.15 + openssl 1.0.0c

I am trying to compile squid from source, using 3.1.15 and openssl 1.0.0c... Server: RedHat 5.5 x86_64 GCC version is 4.1.2 Small mistake on the fixes for OpenSSL 1.0.0d problems. Please try this patch: http://www.squid-cache.org/Versions/v3/3.HEAD/changesets/squid-3-11702.patch I am

Re: [squid-users] Compiling squid-3.1.15 + openssl 1.0.0c

I am trying to compile squid from source, using 3.1.15 and openssl 1.0.0c... Server: RedHat 5.5 x86_64 GCC version is 4.1.2 Small mistake on the fixes for OpenSSL 1.0.0d problems. Please try this patch: http://www.squid-cache.org/Versions/v3/3.HEAD/changesets/squid-3-11702.patch I

[squid-users] Compiling squid-3.1.15 + openssl 1.0.0c

Dear squid users, I am trying to compile squid from source, using 3.1.15 and openssl 1.0.0c... Server: RedHat 5.5 x86_64 GCC version is 4.1.2 Error: (make) /usr/local/src/squid-3.1.15/src/ssl/gadgets.cc:108: undefined reference to `X509_set_issuer_name'

[squid-users] SSL traffic

Dear squid users, we remember to have measured the percentage of bandwitch devoted to SSL in our squid installation, and it was about 10 percent of total traffic. SSL is not cacheable, and I think its use is increasing. I wonder if there is any experience with squid software using SSL

Re: [squid-users] SSL traffic

El 05/04/11 10:31, Amos Jeffries escribió: On 05/04/11 20:01, Víctor José Hernández Gómez wrote: Dear squid users, we remember to have measured the percentage of bandwitch devoted to SSL in our squid installation, and it was about 10 percent of total traffic. SSL is not cacheable, and I think

[squid-users] http_pipelining prefetch ..

Dear squid-users, I have been reading about pipelining (http://en.wikipedia.org/wiki/HTTP_pipelining), and we are thinking to change the pipeline_prefetch directive to on in our Squid-based installation, but have found some notes which prevent us to try it Notes: (Now defaults to off for

[squid-users] work on partition used for cache dir

Hi all, I had planned some work on the ext3 partition used for cache data in our squid 3.1.11 instalation, which should be unomunted and mounted after some filesystem parameters modifications. So I thought it could work the following 1. comment cache_dir line on squid.conf 2. add cache

Re: [squid-users] Asking for advice on obtaining a better throughput.

Hi again, I am using one box (4Gb RAM, modern multicore CPU) for a mono-instance proxy-only (non-caching) squid 3.1.9 version, serving about 2500 clients . CPU is never over 30%, and vmstat output does not show any swapping. 1) The configuration of the instance is very simple indeed: #

Re: [squid-users] xcalloc Fatal (squid 3.1.9)

I have found a message such as: FATAL: xcalloc: Unable to allocate 1 blocks of 536870912 bytes! Looks like a strange big block. My squid versión is 3.1.9. Any suggestion? Probably bug http://bugs.squid-cache.org/show_bug.cgi?id=3113 Please try an upgrade to 3.1.11 to resolve that and a few

[squid-users] xcalloc Fatal (squid 3.1.9)

Hi all, I have found a message such as: FATAL: xcalloc: Unable to allocate 1 blocks of 536870912 bytes! Looks like a strange big block. My squid versión is 3.1.9. Any suggestion? Regards, -- Víctor Hernández Centro de Informatica y Comunicaciones

[squid-users] warning: http reply without date

Hi all, after some time with a proxy only configuration: cache_dir aufs /san/cache 241904 64 512 cache deny all we have changed to : cache_dir aufs /san/cache 241904 64 512 #cache deny all and started to see messages such as: WARNING: An error inside Squid has caused an HTTP reply without

Re: [squid-users] Asking for advice on obtaining a better throughput.

Hi all, Thank you for your quick reply.. [ rest of message skipped for clarity ..] cache_dir aufs /san/cache 241904 64 512 - NOt used cache deny all NP: with a cache_dir configured it *is* used. The cache deny all means that new data will not be added AND that existing data will be removed

[squid-users] Asking for advice on obtaining a better throughput.

Hi all, I am using one box (4Gb RAM, modern multicore CPU) for a mono-instance proxy-only (non-caching) squid 3.1.9 version, serving about 2500 clients . CPU is never over 30%, and vmstat output does not show any swapping. 1) The configuration of the instance is very simple indeed: #