RE: [SQU] single work blocking

#Default configuration:
http_access allow manager localhost
http_access deny manager
http_access deny !Safe_ports
http_access deny CONNECT !SSL_ports
#
# INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS
#
acl blocked url_regex "/etc/squid/blocked.acl"
acl unblocked url_regex "/etc/squid/unblocked.acl"
acl trust url_regex "/etc/squid/trust.acl"

http_access deny blocked
http_access allow unblocked password
#http_access deny blocked
http_access allow trust
http_access allow all password
#
acl blockedsite urlpath_regex -i sussex thestreet
http_access allow blockedsite password
http access deny blockedsite

the single-work-blocking syntax is at the end...can't wait to here what you
think! rf.

-----Original Message-----
From: hno@hem.passagen.se [mailto:hno@hem.passagen.se]
Sent: Sunday, December 24, 2000 4:00 AM
To: Rick Francis
Cc: squid-users@ircache.net
Subject: Re: [SQU] single work blocking

Rick Francis wrote:
>
> acl blockedsite urlpath_regex -i sussex thestreet
> http_access allow blockedsite password
> http access deny blockedsite
>
> here's what i've tried in squid.conf...
>
> yet url that have the word sussex, and 'thestreet,' get blocked?
>
> is there a better method to allowing access to url's (which are mostly
just
> links on other 'allowed' urls) via a single word allowance...meaning...if
> this word exists in the url - then allow access - do not block it?????
>
> thank you very much, rick.

What other http_access lines do you have, and how are these ordered in
relation to the above?

How is "password" defined?

Do you get any error messages in cache.log when Squid is starting?

--
Henrik Nordstrom
Squid Hacker
--
To unsubscribe, see http://www.squid-cache.org/mailing-lists.html
--
To unsubscribe, see http://www.squid-cache.org/mailing-lists.html