Jens-U. Mozdzen changed bug 991680
What Removed Added
CC   jmozdzen@nde.ag

Comment # 7 on bug 991680 from
(In reply to Dominique Leuenberger from comment #4)
> (In reply to Michael Andres from comment #3)
> > 
> > Also the lower table IMO suggests this:
> > > FQDNs
> > >   hostname.domain.com     domain.com                  proxy
> > >   hostname.domain.com     hostname.domain.com         direct
> > >   hostname.domain.com     host.hostname.domain.com    direct
> 
> 
> So the 3rd call does not return as you expect and is documented in the
> Mozilla table - I don't really see why they make a difference in the number
> of levels; that's bogus and rong (and we did indeed not copy this behavior).

who's counting levels? All that is done is matching the tailing characters of
the FQDN.

> Specifying when you talk about the domain and when about the host is the
> only sane solution to know what you want to exluce
> 
> (Think corporate: with domain:
> example.co.uk having this internal network, but www.example.co.uk is hosted
> external.. )

I don't get your point/example? All internal hosts are to be skipped for
proxying, so you'd put ".example.co.uk" into NO_PROXY - but that would include
www.example.co.uk as well. No matter of specifying the leading sub-domain
separator (".") or not.


You are receiving this mail because: