Re: Peer cache connect problem

I will look into that again. Now regarding the cache peer connect timeout
problem I can modify the source to reduce the connect timeout value (is it
hard coded ?), if you can point out where to do so (neighbor.c ?).

thanks

Irfan Akber

Henrik Nordstrom wrote:

> Irfan Akber wrote:
> >
> > I have noticed that it not only fails with having special
> > characters in domain name but also anywhere in the url e.g
> >
> > www.example.net/one&only
>
> Not mine anyway. It happily accepts mostly any characters in the URL
> outside the host name. Tested with
> <http://www.example.com/%e5%e4%f62fa%!"$8()(½§@æ«¢eee> and it got forwarded
> quite nicely.
>
> The validations Squid perform is:
>
> a) The host name must consist of valid charaters [a-z0-9.-]. This check
> is hardcoded and can't be disabled without changing the source.
> b) The urlpath & query must not contain white space. (space or tab).
> This check can be controlled by uri_whitespace in squid.conf. (note: the
> encode setting is flawed in Squid 2.2, use either deny or allow)
>
> --
> Henrik Nordstrom
> Squid hacker
Received on Thu Oct 21 1999 - 18:05:49 MDT