Guido Serassio wrote:
Hi,
One user has reported a very strange problem using cache_peer directive
on 2.7 STABLE6 running on Windows:
When using the following config:
cache_peer 192.168.0.63 parent 3329 0 no-query
cache_peer rea.acmeconsulting.loc parent 3328 3130
the result is always:
vollkom...@gmx.net wrote:
Original-Nachricht
1. DNS lookups fail completely. 204.127.198.4 is among a handful of
external DNS servers I use, whether defined as dns_nameservers in
squid.conf or picked by squid automatically from /etc/resolv.conf:
2009/05/20 21:44:49|
Bundle Buggy has detected this merge request.
For details, see:
http://bundlebuggy.aaronbentley.com/project/squid/request/%3C20090517101856.252BA88D4B%40treenet.co.nz%3E
Project: Squid
Hi,
At 04.38 24/05/2009, Adrian Chadd wrote:
Can you craft a small C program to replicate the behaviour?
Sure, I wrote the following test program:
#include stdio.h
#include Winsock2.h
void main(void)
{
u_short i, converted;
WSADATA wsaData;
struct servent *port = NULL;
char
Can those familiar with the ins and outs of the Vary implementation
have a quick look at
http://www.squid-cache.org/bugs/show_bug.cgi?id=2678
to see if I'm on the right track?
If so, I'll come up with a patch, as well as one for 1947 (which looks
to be quite similar).
Cheers,
--
Mark
Well as Amos said, this isn't the way to call getservbyname().
getservbyname() doesn't translate ports to ports; it translates
tcp/udp service names to ports. It should be returning NULL if it
can't find the service string in the file.
Methinks numeric values shouldn't be handed to
I was using my 3.0 squid.conf, slightly tweaked to suit 3.1, when I encountered
those three issues. I did later try the 3.1 default, again with slight tweaks,
as seen below. The DNS lookup issue persisted with that route:
diff squid.conf.default squid.conf
2,3c2,3
acl localhost src
