On Tue, 2008-01-29 at 08:53 +0100, Juergen.Paulo@xxxxxxxxxxxx wrote: > This syntax worked for squid 2.5: > > acl NO_ICAP_FOR dstdomain XXX > icap_access None deny NO_ICAP_FOR > > in squid 3.0 there comes up: > > FATAL: Did not find ICAP class 'None' referenced on line XXX > > Is there a need to config an icap_class None an how do I do this ? If you do not want ICAP, you can disable it with icap_enable. If you want to fine-tune access for an existing ICAP class, then you should use that class name on the icap_access line. If you are using ICAP services without classes, then you can try to use a service name on the icap_access line, but that may not work. You should probably just add a class for your service. For example, icap_service service_req reqmod_precache 0 icap://10.0.0.104:1344/req icap_class class_req service_req icap_access class_req deny NO_ICAP_FOR icap_access class_req allow all The whole icap_service/class design is rather cumbersome and confusing. It will probably be replaced when we add support for service chaining in Squid3. HTH, Alex.
