OK... Thanks very much for helping me... I'm getting further!
I'm using squidguard to protect my son from all those *nasty* sites out there.
I've got it working now by putting a new rule into the squidGuard.conf to
allow any source to access *.passport.com
But it looked like the result of the previous "default" squidGuard rule was
not being interpreted as I expected by squid...
I was using a redirect in the default squidGuard rule to return http://...
etc.etc.
but squid was taking the bit before the : and looking that up in DNS. Hence
it was looking up http.matson.stc.com
Any clues?
Chris
At 10:05 01/12/2003, Henrik Nordstrom wrote:
>On Mon, 1 Dec 2003, Chris Selwyn wrote:
>
> > Thanks for the reply...
> >
> > 2003/12/01 09:10:00| The request CONNECT login.passport.com:443 is
> ALLOWED,
> > because it matched 'passportdom'
> > 2003/12/01 09:10:00| peerSelectFoo: 'CONNECT http.matson.stc.com'
>
>Looks like you are using a redirector which tries to rewrite the CONNECT
>request in a odd manner..
>
>Regards
>Henrik
>
>
>
>
>---
>Incoming mail is certified Virus Free.
>Checked by AVG anti-virus system (http://www.grisoft.com).
>Version: 6.0.545 / Virus Database: 339 - Release Date: 27/11/2003
Chris Selwyn
Nr. Bath
Somerset
United Kingdom
Email: chris@selwyn-family.me.uk
WWW: http://www.selwyn-family.me.uk
--- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.545 / Virus Database: 339 - Release Date: 27/11/2003Received on Mon Dec 01 2003 - 04:59:51 MST
This archive was generated by hypermail pre-2.1.9 : Thu Jan 01 2004 - 12:00:03 MST