Is either of the two using an url rewriter / redirector helper?
(url_rewrite_program/redirector_program, same directive different names)
Yes, the internal proxy uses squidguard to filter for forbidden urls.
I just tried to disable the redirection to squidguard and now it works.
So the problem s
mån 2008-03-31 klockan 22:12 +0200 skrev Daniel Becker:
> >> but in the log of the upstream proxy it looks like:
> >> TCP_MISS/404 0 CONNECT http:443 - DIRECT/-
> >
> > This is most commonly seen when using a url rewriter helper which
> > incorrectly tries to modify CONNECT requests.
> >
> > Rega
Hi,
thanks for your answer. Just to be sure, that means, that it is not the
fault of my squid configuration, but a configuration error of the peer
webserver?
Regards,
Daniel
On Wed, 2008-03-26 at 14:50 +0100, Daniel Becker wrote:
> in the access.log of the first proxy is appears correct:
> TCP_MISS/000 1557 CONNECT a248.e.akamai.net:443 -
> FIRST_UP_PARENT/192.168.100.11
>
> but in the log of the upstream proxy it looks like:
> TCP_MISS/404 0 CONNECT http:443 - DIREC
Hi,
i have a strange problem with my squid configuration. We use an internal
squid server to authenticate user requests which then sends all requests
not in his local cache to its upstream squid which then retrieves the
content from the internet. This solution works almost perfect, but in
som
