Re: [squid-users] squid.conf.documented instead of squid.conf?

On 04/14/2010 04:02 PM, Boniforti Flavio wrote: > Hello list. > > I'm on Debian SID and wanted to update squid3 to the latest 3.1.1-2 > version. What happened is that dpkg returned me following error: > > Configurazione di squid3 (3.1.1-2)... > sed: errore di lettura su stdin: Is a directory > dp

[squid-users] OpenBSD 4.6: Squid 3.1.3 compilation error (patch attached)

Hello! I'm getting some error when compiling Squid 3.1.3 on OpenBSD 4.6 due to a redefinition of FD_SETSIZE in compat/fdsetsize.h. Patch attached which fixed this for me. Greetings, Matthias Fix redefinition error for FD_SETSIZE on OpenBSD 4.6. --- compat/fdsetsize.h.orig Mon May 3 12:56:05

Re: [squid-users] OpenBSD 4.6: Squid 3.1.3 compilation error (patch attached)

On 05/03/2010 02:04 PM, Amos Jeffries wrote: > Silamael wrote: >> Hello! >> >> I'm getting some error when compiling Squid 3.1.3 on OpenBSD 4.6 due to >> a redefinition of FD_SETSIZE in compat/fdsetsize.h. >> Patch attached which fixed this for me. >>

Re: [squid-users] OpenBSD 4.6: Squid 3.1.3 compilation error (patch attached)

On 05/03/2010 02:04 PM, Amos Jeffries wrote: > Thanks for the thought, but... > > Code in Squid is NOT permitted to include system headers before the > FD_* compat code. Kernel defines will be allocated with incompatible > size and overflows happen. > > Can you provide a full compiler trace of t

Re: [squid-users] OpenBSD 4.6: Squid 3.1.3 compilation error (patch attached)

On 05/04/2010 01:42 AM, Brett Lymn wrote: > On Mon, May 03, 2010 at 05:08:29PM +0200, Silamael wrote: > >> Fix include order to ensure that FD_SETSIZE from the compat/fdsetsize.h is >> set >> before it is set by sys/select.h (included by stdlib.h). >> > > To

[squid-users] [PATCH] Squid 3.1.4 not building under OpenBSD 4.6

Hello! Yesterday i tried to build the new version of Squid on OpenBSD 4.6. Unfortunately there's some problem in src/mem.cc. new_pool_limit is of type size_t which is a long unsigned int. In line 359 a -1 is written into new_pool_limit. Newer g++ versions seems to accept this as valid but OpenBSD'

Re: [squid-users] [PATCH] Squid 3.1.4 not building under OpenBSD 4.6

On 06/02/2010 08:54 AM, Silamael wrote: > Hello! > > Yesterday i tried to build the new version of Squid on OpenBSD 4.6. > Unfortunately there's some problem in src/mem.cc. new_pool_limit is of > type size_t which is a long unsigned int. In line 359 a -1 is written > into

Re: [squid-users] Build Fail for 3.1.4 on IBM PowerPC64

On 06/18/2010 08:27 PM, Steve wrote: > Hi > I am getting a compile error with 3.1.4 on IBM Power ppc64 running Red Hat > Enterprise Linux AS release 4 (Nahant Update 8). > The error is :- > mem.cc: In function `void memConfigure()': > mem.cc:359: warning: converting of negative value `-0x00

[squid-users] Question about SquidGuard and blocking pages

Hello! We're using SquidGuard for blocking certain URLs. Now, the problem is that SquidGuard redirects to some internal://.../error-access-denied URL, but in this page this internal URL is shown as blocked URL instead of the original URL. Is that any configuration problem or did i stumble over som

Re: [squid-users] Question about SquidGuard and blocking pages

On 07/22/2010 03:24 PM, Beavis wrote: > looks like a config is missing. in my setup i have prepared the > internal access-denied page and put a fqdn on use an internal dns zone > you have to resolv it. squid does pretty good on filtering, and it > includes filter via IP. try to have the page with u

Re: [squid-users] Question about SquidGuard and blocking pages

On 07/24/2010 06:10 AM, Amos Jeffries wrote: > Yes. This is why the interface is called URL re-write. > It alters the URL being fetched in-transit to whatever the re-writer > sends back. Squid then fetches that URL from the server in the Host: > header or a cache_peer. > > Another catch is that al

[squid-users] OpenBSD: Compile error in tools.cc, line 70

Hi there! Yesterday i tried to compile the brand new version 3.1.6 on OpenBSD. Got some compiler error on src/ip/tools.cc, line 70. Seems that at least on OpenBSD the include of unistd.h is missing. If I add #include myself, tools.cc compiles fine. -- Matthias

Re: [squid-users] Problem: unable to compile squid with TPROXY, broken libcap?

On 08/25/2010 04:34 PM, Leonardo wrote: > Hi all, > > I am re-posting this as a separate thread so to handle one problem at once. > > My aim is to use Squid with TPROXY capabilities enabled, so I am > trying to build the latest source (3.1.6) on Debian Lenny 5.0.5: > ./configure --enable-linux-ne

Re: [squid-users] Squid 3.1.16: Startup problem on OpenBSD 4.9

On 11/03/2011 03:50 PM, Silamael wrote: > Hello! > > Sometimes starting Squid in OpenBSD 4.9 fails with the following message > in cache.log: > >> diskHandleWrite: FD 10: disk write error: (14) Bad address > > So far, I was unable to get some more information when en

Re: [squid-users] Squid 3.1.16: Startup problem on OpenBSD 4.9

On 11/03/2011 05:34 PM, Silamael wrote: > On 11/03/2011 03:50 PM, Silamael wrote: >> Hello! >> >> Sometimes starting Squid in OpenBSD 4.9 fails with the following message >> in cache.log: >> >>> diskHandleWrite: FD 10: disk write error: (14) Bad address

Re: [squid-users] Problem compiling Squid 3.1.18 on Ubuntu 10.04 LTS - store.cc

On 12/06/2011 04:09 AM, Amos Jeffries wrote: > It is only affecting adaptation (ICAP/eCAP) builds, so if you can run > happily without those features use --disable, or comment out line 376 of > src/store.cc. > > > Thank you for the testing offer. We can replicate it already so the only > help nee

[squid-users] Question about refresh_pattern and TCP_MEM_HIT

Hello, I have a simple question about refresh_pattern and TCP_MEM_HIT. Given the following configuration: refresh_pattern foo.example.org 0 0% 0 refresh_pattern . 0 20% 14400 Now, if i fetch something from foo.example.org i get a TCP_CLIENT_REFRESH_MISS/200 The following request for the same url

Re: [squid-users] Question about refresh_pattern and TCP_MEM_HIT

On 09/19/2012 02:12 AM, Amos Jeffries wrote: > On 19/09/2012 9:10 a.m., Eliezer Croitoru wrote: >> On 9/18/2012 6:01 PM, Silamael wrote: >>> refresh_pattern foo.example.org 0 0% 0 >>> refresh_pattern . 0 20% 14400 >>> >>> Now, if i

Re: [squid-users] Question about refresh_pattern and TCP_MEM_HIT

On 09/19/2012 10:12 AM, Amos Jeffries wrote: > On 19/09/2012 6:51 p.m., Silamael wrote: >> >> Ok, so if a response contains valid headers concerning caching, these >> are taken instead of using the matching refresh_pattern? So, if i want >> some URLs being served complet

Re: [squid-users] WARNING: no_suid: setuid(0): (1) Operation not permitted

On 02/01/2013 01:09 AM, Amos Jeffries wrote: > Hmm. Yes the warning is new since we started adding debugs() about > failed system calls to display reviously hidden system errors. > > Looking at all the documentation about setuid() and seteuid() I'm > wondering if this was supposed to be seteuid(0)

[squid-users] Squid 3.2: squid -z forking?

Hi! I just noticed that the squid -z command seems to fork and the child is creating the cache directories. The parent immediatly returns with exit code 0. There's a race for cases like: squid -z; squid Is this behaviour intended? Greetings, Matthias

Re: [squid-users] Squid 3.2: squid -z forking?

On 02/06/2013 02:05 AM, Amos Jeffries wrote: > Partially. The parent returning immediately is not agood thing. BUT, > "squid -z ; squid" is not a good way to do things even if it did. If > that were possible we would simply have made squid startup perform the > -z operations by default. > > squid

Re: [squid-users] Squid 3.2: squid -z forking?

On 02/06/2013 10:42 PM, Alex Rousskov wrote: > Yes, it is. In old Squids, -z implied no-daemon mode. Then folks wanted > to use SMP macros in their configurations, including their cache_dir > lines. Those macros require SMP mode (each Squid kid gets its own set of > macro values) so we removed that

[squid-users] Squid 3.2: Mismatch of code and release notes for ACL types

Hi there! I just stumbled over the part in the release notes where it's said that the ACL types myip and myport have been renamed to localip and localport. But these new types do not work! In the source code it's still myip and myport. Greetings, Matthias

[squid-users] Question about forward.cc and possible patch

Hi there! Last week we had a problem that a cache peer's DNS resolved to 13 v6 and 13 v4 addresses but the system lacked IPv6 connectivity at all. While debugging the problem (the solution was just to increase forward_max_tries) I stumbled over a line in forward.cc where n_tries is always checked

Re: [squid-users] Question about forward.cc and possible patch

On 05/13/2013 10:22 AM, Amos Jeffries wrote: > Please submit your change for audit: > http://wiki.squid-cache.org/MergeProcedure#Submission_Format > > Amos Done :)

[squid-users] Squid 3.1.8: Removing cache_dir + SIGHUP --> disk cache still in use

Hello, I just debugged something i think it probably not working as intended: I start Squid with some cache_dir option in its configuration file. Afterwards i remove the cache_dir line from the config and send Squid a SIGHUP (or do squid -k reconfigure). When accessing further URLs after this, i s

[squid-users] Squid 3.1.11 compilation problem on OpenBSD 4.9

I together, When compiling Squid 3.1.11 on the current OpenBSD, i get an error because netinet/in.h is not included in include/util.h before including arpa/inet.h. Attached is a simple patch fixing this issue. -- Matthias --- include/util.h.orig Thu Mar 3 14:04:15 2011 +++ include/util.h T

Re: [squid-users] Fwd: squid-3.2.0.6 - make issue on OpenBSD 4.8 - 64 bit

On 04/05/2011 12:05 PM, Indunil Jayasooriya wrote: > Hi ALL, > > I downloaded squid-3.2.0.6 from below URL > > http://www.squid-cache.org/Versions/v3/3.2/squid-3.2.0.6.tar.gz > > > I ran (this is on OpenBSD 4.8 - 64 bit) > > ./configure > > It went fine. > > Then, ran > > make > > stoped a

[squid-users] Question about Connection: keep-alive and Proxy-Connection: keep-alive

Hello there, We have some application encountering problems if it's communicating via Squid: - the application sends a HTTP/1.1 HEAD-Request with Proxy-Connection: keep-alive set - Squid then forwards the request to the server with Connection: keep-alive - the server replies with the headers and a

[squid-users] Squid 3.1.16: Startup problem on OpenBSD 4.9

Hello! Sometimes starting Squid in OpenBSD 4.9 fails with the following message in cache.log: > diskHandleWrite: FD 10: disk write error: (14) Bad address So far, I was unable to get some more information when enabling some debug options. The only bit of information I was able to gather was a kt

[squid-users] Squid 3.1 Release Date

Hello there! Is there any date when Squid 3.1 will be official released? Thanks in advance! -- Matthias

Re: [squid-users] Squid 3.1 Release Date

Francois Cami wrote: > On Tue, Mar 3, 2009 at 8:32 AM, Silamael wrote: >> Is there any date when Squid 3.1 will be official released? >> Thanks in advance! > > http://wiki.squid-cache.org/ReleaseProcess#head-eea0e990c0003af12917552175691a5120980cdd > Thanks for th

Re: [squid-users] Squid 3.1 Release Date

Amos Jeffries wrote: > We don't exactly date things here. With everyone working on voluntary > time its unpredictable. Though there has been a fairly regular 4-week > cycle for new X.Y.0.z beta releases. > > For planning and upgrade testing, 3.1.0.6 is a fairly stable point to > begins with. > >

[squid-users] Using DNSSEC in Squid

Hello! Is there any possibility at moment to use DNSSEC in Squid? We want to present a special error page if a DNS answer is received which fails the DNSSEC check. Are there any built-in features, patches or anything else to realize this? Thanks in advance! Greetings, Matthias

[squid-users] Running Squid 3.1.0.7 without disk cache

Hello, Is there a possibility to run Squid without using a disk cache? Former versions had the null module for storeio which could be used for that. Now there is no such null module. Thanks in advance! -- Matthias

Re: [squid-users] Running Squid 3.1.0.7 without disk cache

Amos Jeffries wrote: >> Hello, >> >> Is there a possibility to run Squid without using a disk cache? >> Former versions had the null module for storeio which could be used for >> that. Now there is no such null module. >> Thanks in advance! > > Running without disk cache is now the default :) > >

[squid-users] Question about: Changes to squid-cache.org FTP servers

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello there, Will the paths on the HTTP-Server also change? - -- Matthias -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkpKKn0ACgkQGgHcOSur6dRwKQCcCTqqLNuU

Re: AW: AW: [squid-users] Squid 3.1.0.11 beta is available

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Zeller, Jan wrote: > Hi Amos, > > thank you very much for your patch ! Great ! > Applied it like this : > > $ patch -p0 < b9052.patch > patching file src/client_side.cc > Hunk #1 succeeded at (offset 81 lines). > > $ make && make install - th

Re: AW: AW: AW: AW: AW: [squid-users] Squid 3.1.0.11 beta is available

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Zeller, Jan wrote: > Hi Amos, > > I now explicitly enabled > > --enable-stacktraces Enable automatic call backtrace on fatal errors > > during the build and added CFLAGS="-g -ggdb" in front of ./configure > but the result seems to be the same... >

[squid-users] Squid 3.1.0.12: assertion failed in http.cc, line 705: !eof

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello together, Squid 3.1.0.12 runs pretty well except this assertion problem i've also seen on the mailing list for Squid 3.0 Stable17. Every time the assertion fails, before following is logged: > ... HttpMsg.cc(157) parse: first line of HTTP messag

Re: [squid-users] Squid crashes - Create Bugreport?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thomas Jackowski wrote: > Hi, > > Squid crashes with this message in cache.log: > > 2009/08/11 06:54:31| assertion failed: store_client.cc:430: > "STORE_DISK_CLIENT == getType()" > 2009/08/11 06:54:35| Starting Squid Cache version 3.0.STABLE8 for > x

[squid-users] Squid 3.1.0.13: assertion failed: src/store_client.cc:430: "STORE_DISK_CLIENT == getType()"

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello everyone, We're running Squid version 3.1.0.12 with the fix for the DoS vulnerability applied and have from time to time crashes due to this assertion: assertion failed: src/store_client.cc:430: "STORE_DISK_CLIENT == getType()" I searched in Sq

[squid-users] Squid 3.1.12 - Parent Proxy and DNS queries

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello everyone! We're running a Squid version 3.1.12 with a cache peer configured. Furthermore Squid is configured to forward every request directly to the cache peer. Nevertheless Squid is doing a DNS query for every requests received. At this point

Re: [squid-users] Squid 3.1.12 - Parent Proxy and DNS queries

Amos Jeffries wrote: > This is usually a configuration problem. > > Please provide your squid.conf file contents (minus empty and comment > lines) > > Amos Hello Amos, Here is our configuration. Thank you for your help. -- Matthias # # WARNING: Do not edit this file, it has been automatically

Re: [squid-users] Squid 3.1.12 - Parent Proxy and DNS queries

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Silamael wrote: > Amos Jeffries wrote: >> This is usually a configuration problem. >> >> Please provide your squid.conf file contents (minus empty and comment >> lines) >> >> Amos No one has some i

Re: [squid-users] Squid 3.1.12 - Parent Proxy and DNS queries

Amos Jeffries wrote: > ... >anything resolving to 127.0.0.1 on this host is not necessarily > resolving to 127.0.0.1 on any other host (ie the parent proxy) > > NP: having a DNS server resolve 127.0.0.1 for anything public is very > nasty. Hi Amos, Thank you for your help. Meanwhile i did

Re: [squid-users] Squid 3.1.12 - Parent Proxy and DNS queries

Amos Jeffries wrote: > That seems very strange. Very strange. > > Squid using internal DNS resolver sends out UDP packets and waits for a > reply positive or negative. Using that. > > The NXDOMAIN results make sense if we assume they come back with some > TTL so short Squid needs to run through t

[squid-users] Squid 3.1: ICAP and Round Robin for ICAP Services

Hello together, Is there any possiblity to realize a round robin scheduling for requests sent to ICAP services? Goal is to forward each HTTP request to the next available ICAP service due to load balancing issues. As far as i read the configuration manual, there is no option to to this. Can this b

Re: [squid-users] Squid 3.1: ICAP and Round Robin for ICAP Services

Silamael wrote: > Hello together, > > Is there any possiblity to realize a round robin scheduling for requests > sent to ICAP services? Goal is to forward each HTTP request to the next > available ICAP service due to load balancing issues. > As far as i read the configuration m

Re: [squid-users] Squid-3.1: comm_open: socket failure: (97) Address family not supported by protocol

Amos Jeffries wrote: > You have IPv6 disabled in your system somehow. > > Squid opens IPv4/IPv6 hybrid sockets to receive and send both v4 and v6 > traffic in one socket for simplicity and ease of transition. If that fails > like in your case it falls back to IPv4-only sockets. > > I recommend re

Re: [squid-users] Problem with cache_peer - cannot open websites

On 11/16/2009 01:45 PM, Werner Müller wrote: The Problem is, that i cannot reach a Server over the IP: with this cache_peer entry i get a failure: cache_peer 1.1.1.1 parent 3128 0 default no-query no-digest The localhost entry was only a test. But it's very strange that it works with the local

[squid-users] Squid 3.1.0.14: ICAP REQMOD - Not returning 403 error page to client

Hello together! We're using the ICAP interface of Squid for some request filtering. When the ICAP server denies access to a page, it responds with an 403 HTTP return code and some error page. Squid only forwards the return code to the client but the body of the response is not forwarded. Is th

Re: [squid-users] Squid 3.1.0.14: ICAP REQMOD - Not returning 403 error page to client

On 11/18/2009 01:59 AM, Amos Jeffries wrote: Maybe yes, maybe no What configuration are you referring too? Is the ICAP server setting Content-Length correctly to the size of the error page body? Hello Amos, As far as i can say, the Content-Length is set properly. I have some simple

Re: [squid-users] Squid 3.1.0.14: ICAP REQMOD - Not returning 403 error page to client

On 11/18/2009 08:22 AM, Silamael wrote: On 11/18/2009 01:59 AM, Amos Jeffries wrote: Maybe yes, maybe no What configuration are you referring too? Is the ICAP server setting Content-Length correctly to the size of the error page body? Hello Amos, As far as i can say, the Content-Length

Re: [squid-users] Squid 3.1.0.14: ICAP REQMOD - Not returning 403 error page to client

On 11/23/2009 09:41 AM, Silamael wrote: Hello Amos, I found out that my test creates an invalid Encapsulated header. After fixing it, squid dies with an assertion failure in BodyPipe::undoCheckout(). Attached you find the cache.log of my test. Greetings, Matthias Hello together, I searched

Re: [squid-users] Squid 3.1.0.16 beta is available

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/02/2010 02:33 AM, The Doctor wrote: > Squid 3.1.16 is not working on my FreeBSD 7.2 Box. > "not working" is a quite helpfull problem description... - -- Matthias -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using Gn

[squid-users] Squid 3.1.0.16: assertion failure in src/peer_select.cc, line 627

Hello, I just built the new version of Squid. When starting, Squid dies instantly with an assertion failure in peer_select.cc, line 627. Apparently in peer_select.cc "PINNED" is missing in the hier_strings. PINNED is in enums.h but not in peer_select.cc, so the list of constants and the string arr

[squid-users] Error page errors/ca/ERR_CACHE_ACCESS_DENIED empty

Hello! In Squid 3.1.0.16 the error file errors/ca/ERR_CACHE_ACCESS_DENIED is completely empty. Greetings, Matthias

Re: [squid-users] Squid 3.1.0.16: assertion failure in src/peer_select.cc, line 627

On 02/02/2010 11:38 AM, Amos Jeffries wrote: > Sorry about that. This was caught shortly after the release was > announced. The bundles have since been updated. > > Please re-download and re-build your copy of 3.1.0.16. If you are using > a pre-packaged version please contact the package maintaine

Re: [squid-users] Error page errors/ca/ERR_CACHE_ACCESS_DENIED empty

On 02/02/2010 11:53 AM, Amos Jeffries wrote: > Strange. I can't see anything obviously wrong with that languages source > files. > > For now, copying templates/ERR_CACHE_ACCESS_DENIED to > ca/ERR_CACHE_ACCESS_DENIED will get around this. > > I'll keep an eye on the snapshots and see if its broken

[squid-users] Orig. request HTTP/1.0, outgoing request HTTP/1.1

Hello together, Just build the new Squid 3.1.0.18 and noticed that now, Squid does an HTTP/1.1 request to the server even if the client just sent an HTTP/1.0 request. Previous versions of Squid did not do that. Is this intended or did i stumble over some minor bug? -- Matthias

Re: [squid-users] Orig. request HTTP/1.0, outgoing request HTTP/1.1

On 03/15/2010 01:37 PM, Amos Jeffries wrote: > RFC 2616 compliance has nearly been reached in 3.1. > Squid can now talk HTTP/1.1 to web servers. Upgrading requests like you > saw is the final requirement to be met in that area. Hi Amos, Thank you for the quick answer :) -- Matthias

[squid-users] X-Forwarded-For and Squid 3.0

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello! Are there any plans to implement the X-Forwarded-For feature in Squid3? We had to use Squid3 due to some ICAP project stuff and we will need the X-Forwarded-For feature for some other stuff too... Greetings, Matthias -BEGIN PGP SIGNATURE--

Re: [squid-users] X-Forwarded-For and Squid 3.0

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Amos Jeffries wrote: > Yes. It is already done and in Squid 3.1. > > We've had a fair number of annoyances found with the 3.1.0.2 packages > not including everything they needed for the new code. One more in > todays snapshot. So for testing I'd advis

Re: [squid-users] Re: Problem compiling Squid 3.1.11 or 3.1.12 on OpenBSD 4.8

On 21-Apr-11 16:07, EzyMike wrote: > Indunil Jayasooriya wrote: >> On Thu, Apr 21, 2011 at 1:54 PM, EzyMike wrote: >>> Hi! >>> >>> I have a problem compiling squid 3.1.11 or 3.1.12 on a OpenBSD 4.8 box. >>> When preparing to replace a OpenBSD 4.6 box with a 4.8, the compilation