[squid-users] squid-3.0-PRE3-20050827 parseConfigFile "unrecognized:" errors on launch

hi all,

i've been running Squid25-STABLE10, built from src on OSX 10.4.2, with no
problems.

latest use is as a transparent proxy front-end to Privoxy & Tor ...

noticing 'activity' on the site, i decided to give squid 30 a try ...

i DL'd & built squid-3.0-PRE3-20050827.

builds & executes w/ no errors, resulting in:

% ps -ax | grep squid
        18446 ?? Ss 0:00.01 /usr/local/squid30/sbin/squid -X -f
/var/Settings/SquidProxy/squid.conf

% otool -L squid
        /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version
88.0.0)
        /usr/local/ssl/lib/libssl.0.9.7.dylib (compatibility version 0.9.0, current
version 0.9.7)
        /usr/local/ssl/lib/libcrypto.0.9.7.dylib (compatibility version 0.9.0, current
version 0.9.7)
        /usr/lib/libresolv.9.dylib (compatibility version 1.0.0, current version
365.0.0)
        /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 7.3.0)
        /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0)
        /usr/lib/libmx.A.dylib (compatibility version 1.0.0, current version 92.0.0)

BUT, in my logs I note that the launch is 'choking' on my prior/existing conf @:

        ...
        2005/08/27 10:12:15.732| parseConfigFile: 'squid.conf' line 20 unrecognized:
'httpd_accel_host virtual'
        2005/08/27 10:12:15.732| parseConfigFile: 'squid.conf' line 21 unrecognized:
'httpd_accel_port 80'
        2005/08/27 10:12:15.732| parseConfigFile: 'squid.conf' line 22 unrecognized:
'httpd_accel_with_proxy on'
        2005/08/27 10:12:15.732| parseConfigFile: 'squid.conf' line 23 unrecognized:
'httpd_accel_uses_host_header on'
        2005/08/27 10:12:15.732| parseConfigFile: 'squid.conf' line 90 unrecognized:
'header_access Allow allow local_LAN'
        2005/08/27 10:12:15.732| parseConfigFile: 'squid.conf' line 91 unrecognized:
'header_access Authorization allow local_LAN'
        2005/08/27 10:12:15.732| parseConfigFile: 'squid.conf' line 92 unrecognized:
'header_access WWW-Authenticate allow local_LAN'
        2005/08/27 10:12:15.732| parseConfigFile: 'squid.conf' line 93 unrecognized:
'header_access Cache-Control allow local_LAN'
        2005/08/27 10:12:15.732| parseConfigFile: 'squid.conf' line 94 unrecognized:
'header_access Content-Encoding allow local_LAN'
        2005/08/27 10:12:15.732| parseConfigFile: 'squid.conf' line 95 unrecognized:
'header_access Content-Length allow local_LAN'
        2005/08/27 10:12:15.732| parseConfigFile: 'squid.conf' line 96 unrecognized:
'header_access Content-Type allow local_LAN'
        2005/08/27 10:12:15.732| parseConfigFile: 'squid.conf' line 97 unrecognized:
'header_access Date allow local_LAN'
        2005/08/27 10:12:15.732| parseConfigFile: 'squid.conf' line 98 unrecognized:
'header_access Expires allow local_LAN'
        2005/08/27 10:12:15.732| parseConfigFile: 'squid.conf' line 99 unrecognized:
'header_access Host allow local_LAN'
        2005/08/27 10:12:15.732| parseConfigFile: 'squid.conf' line 100 unrecognized:
'header_access If-Modified-Since allow local_LAN'
        2005/08/27 10:12:15.732| parseConfigFile: 'squid.conf' line 101 unrecognized:
'header_access Last-Modified allow local_LAN'
        2005/08/27 10:12:15.732| parseConfigFile: 'squid.conf' line 102 unrecognized:
'header_access Location allow local_LAN'
        ...

i've read through:

        http://www.squid-cache.org/Doc/FAQ/FAQ_long.html
        ViSolve's Squid 3.0 Configuration Manual
and,
        searched the list archives ...

and all indications are that these directives should be ok.

have i missed a known issue, or am i missing something obvious in the 'upgrade'?

cheers,

richard
Received on Sat Aug 27 2005 - 11:27:46 MDT