AW: [squid-users] https from different Subnet not working

> -----Ursprüngliche Nachricht-----
> Von: adrian.chadd_at_gmail.com [mailto:adrian.chadd_at_gmail.com] Im Auftrag
> von Adrian Chadd
> Gesendet: Dienstag, 14. Juli 2009 11:16
> An: Jarosch, Ralph
> Cc: squid-users_at_squid-cache.org
> Betreff: Re: [squid-users] https from different Subnet not working
>
> 2009/7/14 Jarosch, Ralph <Ralph.Jarosch_at_justiz.niedersachsen.de>:
> > This is the latest support squid-2 version for RHEL5.3
> >
> > An I want to use the dnsserver
>
> Right. Well, besides the other posters' response about the cache peer
> setup being a clue - you're choosing a peer based on source IP as far
> as I can tell there - which leads me to think that perhaps that
> particular cache has a problem. You didn't say which caches they were
> in your config or error message so we can't check whether they're the
> same or different.
>
Ok sorry.
The current way for an website request is

Client --> headproxy(10.37.132.2) --> my cache proxys (10.37.132.5/6/7/8) --> proxy off our isp --> internet

The error message come from the isp proxy which tell when I request something like https://www.ebay.com

 The requested URL could not be retrieved
 ----------------------------------------------------------------------
 ---------- While trying to retrieve the URL: http.yyy.xxx:443 The yyy.xxx is our local domain
 following error was encountered:
 Unable to determine IP address from host name for The dnsserver
 returned:
 Name Error: The domain name does not exist.
 This means that:
  The cache was not able to resolve the hostname presented in the URL.
  Check if the address is correct.
 Your cache administrator is webmaster.
 ----------------------------------------------------------------------
 ---------- Generated Tue, 14 Jul 2009 08:10:39 GMT by xxxxxxx the answer come from the isp
 (squid/2.5.STABLE12)

I´ve made an tcpdump between our headproxy and our cacheproxy´s an there I can see that the headproxy change the request from https//www.ebay.com to https.our.domain.com
     

> But since yo'ure using a supported squid for RHEL5.3, why don't you
> contact Redhat for support? That is why you're paying them for.
>
>
> adrian
Received on Tue Jul 14 2009 - 09:40:35 MDT