Re: [squid-users] Broken upgrade from 2.1 to 2.4

Somebody hasn't read the FAQ on interception caching lately.

The other httpd_accel options are missing.

Phil N wrote:

> I upgraded a 2.1.x system to 2.4.STABLE2 this morning. After making
> basic configuration changes to the default squid.conf (there was enough
> difference in the 2.1 - 2.4 versions that I couldn't use the old conf.)
> I now cannot get any HTTP requests thru the proxy. Removing the proxy
> from the ipchains rules (REDIRECT 3128) gets around the problem and
> users can work.
>
> If you look within the snippet from the log file (debug on) for the
> request http://www.toosan.com/index.htm, there are lines such as
> "2001/09/04 16:42:21| Invalid URL: /index.htm" and "2001/09/04 16:42:21|
> created entry 0x8412ad8: 'X-Squid-Error: ERR_INVALID_URL 0' " and
> "2001/09/04 16:42:21| HTTP/1.0 400 Bad Request^M" and "2001/09/04
> 16:42:21| destroying entry 0x8412c00: 'X-Squid-Error: ERR_INVALID_URL 0'
> "
>
> Any ideas why I can't get requests through the proxy? What is up with
> the "INVALID_URL" errors?
>
> Thanks! Phil
>
> [root@mail logs]# cat /usr/local/squid/etc/squid.conf |grep -v '#'
>
> hierarchy_stoplist cgi-bin ?
> acl QUERY urlpath_regex cgi-bin \?
> no_cache deny QUERY
> cache_dir ufs /var/squid/cache 100 16 256
> cache_access_log /var/squid/logs/access.log
> cache_log /var/squid/logs/cache.log
> cache_store_log /var/squid/logs/store.log
> debug_options ALL,2
>
> acl all src 0.0.0.0/0.0.0.0
> acl manager proto cache_object
> acl localhost src 127.0.0.1/255.255.255.255
> acl SSL_ports port 443 563
> acl allowed_hosts src 10.0.0.0/255.255.255.0
> acl CONNECT method CONNECT
> http_access allow all
> cache_mgr pnewlon@toosan.com
> httpd_accel_with_proxy off

                                   --
                      Joe Cooper <joe@swelltech.com>
                  Affordable Web Caching Proxy Appliances
                         http://www.swelltech.com
Received on Wed Sep 05 2001 - 12:02:46 MDT