Re: [squid-users] Odd behavior on CNAME

2019-01-14 Thread Alex Rousskov
On 1/14/19 3:51 AM, Felix Falk wrote:

> I have a linkchecker running over Squid as forwardproxy. One Site is not
> longer existing but DNS still has a CNAME Record except the CNAME is
> pointing nowhere:
> 
>> $ host de.sitestat.com
>> de.sitestat.com is an alias for wildcard.sitestat.com.
>> $ host wildcard.sitestat.com.
>> $ 
> 
> If called via curl:
>> $ curl --proxy forwardproxy:3128 -v http://de.sitestat.com/
>> * About to connect() to proxy forwardproxy.rz.babiel.com port 3128 (#0)
>> *   Trying 192.168.110.215...
>> * Connected to forwardproxy.rz.babiel.com (192.168.110.215) port 3128 (#0)
>> > GET http://de.sitestat.com/ HTTP/1.1
>> > User-Agent: curl/7.29.0
>> > Host: de.sitestat.com
>> > Accept: */*
>> > Proxy-Connection: Keep-Alive
>> > 
> 
> The connection and this curl stays open for literally infinitely.
> (tested for 3 days).
> 
> In the Squid access.log nothing shows up. My cache.log has:
>> 2019/01/14 11:30:31 kid1| ipcacheParse: No Address records in response
> to 'de.sitestat.com'
> 
> Any ideas how to solve this or is this simply a bug?

I suggest reporting a bug if you can reproduce with the latest v4
release. Posting a (link to) compressed ALL,9 cache.log to bugzilla may
speed up triage.

FWIW, using v5-based code, your test worked for me with an immediate
ERR_CANNOT_FORWARD error and the following level-1 cache.log entry:

2019/01/14 09:04:58| DNS error while resolving de.sitestat.com: No valid
address records

Alex.
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users


Re: [squid-users] Odd behavior on CNAME

2019-01-14 Thread Felix Falk
Hi,

I probably should mention:
- other working sites are doing fine over the proxy
- domains without any record are throwing the mentioned error properly

Felix

Am 14. Januar 2019 16:09:59 MEZ schrieb elie...@ngtech.co.il:
>It should return:
>
>… page.
>And it takes 100 ms.
> 
>Can you re-test it?
>Also make sure what happens if you run the same command from within the
>proxy host and not remotely.
> 
>Another option is that there is something else between you and the
>proxy but it sound odd.
> 
>Eliezer
> 
>
>  Eliezer Croitoru
>Linux System Administrator
>Mobile: +972-5-28704261
>Email:   elie...@ngtech.co.il
>
> 
>From: squid-users  On Behalf
>Of Felix Falk
>Sent: Monday, January 14, 2019 12:51
>To: squid-users@lists.squid-cache.org
>Subject: [squid-users] Odd behavior on CNAME
> 
>Hi,
>I have a linkchecker running over Squid as forwardproxy. One Site is
>not longer existing but DNS still has a CNAME Record except the CNAME
>is pointing nowhere:
>
>> $ host de.sitestat.com
>> de.sitestat.com is an alias for wildcard.sitestat.com.
>> $ host wildcard.sitestat.com.
>> $ 
>
>If called via curl:
>> $ curl --proxy forwardproxy:3128 -v http://de.sitestat.com/
>> * About to connect() to proxy forwardproxy.rz.babiel.com port 3128
>(#0)
>> *   Trying 192.168.110.215...
>> * Connected to forwardproxy.rz.babiel.com (192.168.110.215) port 3128
>(#0)
>> > GET http://de.sitestat.com/ HTTP/1.1
>> > User-Agent: curl/7.29.0
>> > Host: de.sitestat.com
>> > Accept: */*
>> > Proxy-Connection: Keep-Alive
>> > 
>
>The connection and this curl stays open for literally infinitely.
>(tested for 3 days).
>
>In the Squid access.log nothing shows up. My cache.log has:
>> 2019/01/14 11:30:31 kid1| ipcacheParse: No Address records in
>response to 'de.sitestat.com'
>
>Any ideas how to solve this or is this simply a bug?
>
>Felix

-- 
Felix Falk
@theftf
http://thef.tf/
+492022623399

OpenPGP Fingerprint: B8F6 590B F4B1 19F6 AE94 D24E D91B 960B 97E1 6444

Von meinem mobilen Plemplemplicator gesendet___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users


Re: [squid-users] Odd behavior on CNAME

2019-01-14 Thread eliezer
It should return:

… page.
And it takes 100 ms.
 
Can you re-test it?
Also make sure what happens if you run the same command from within the proxy 
host and not remotely.
 
Another option is that there is something else between you and the proxy but it 
sound odd.
 
Eliezer
 

  Eliezer Croitoru
Linux System Administrator
Mobile: +972-5-28704261
Email:   elie...@ngtech.co.il

 
From: squid-users  On Behalf Of 
Felix Falk
Sent: Monday, January 14, 2019 12:51
To: squid-users@lists.squid-cache.org
Subject: [squid-users] Odd behavior on CNAME
 
Hi,
I have a linkchecker running over Squid as forwardproxy. One Site is not longer 
existing but DNS still has a CNAME Record except the CNAME is pointing nowhere:

> $ host de.sitestat.com
> de.sitestat.com is an alias for wildcard.sitestat.com.
> $ host wildcard.sitestat.com.
> $ 

If called via curl:
> $ curl --proxy forwardproxy:3128 -v http://de.sitestat.com/
> * About to connect() to proxy forwardproxy.rz.babiel.com port 3128 (#0)
> *   Trying 192.168.110.215...
> * Connected to forwardproxy.rz.babiel.com (192.168.110.215) port 3128 (#0)
> > GET http://de.sitestat.com/ HTTP/1.1
> > User-Agent: curl/7.29.0
> > Host: de.sitestat.com
> > Accept: */*
> > Proxy-Connection: Keep-Alive
> > 

The connection and this curl stays open for literally infinitely. (tested for 3 
days).

In the Squid access.log nothing shows up. My cache.log has:
> 2019/01/14 11:30:31 kid1| ipcacheParse: No Address records in response to 
> 'de.sitestat.com'

Any ideas how to solve this or is this simply a bug?

Felix
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users