By http_access rules.
Note that deny_info looks at the last ACL on the http_access line, and
any acls used on a http_access line needs to be defined.
To create ACLs that is only used for selecting deny_info messages in a
more intuitive manner, create simple acls that match everything (i.e.
like the "all" acl).
Regards
Henrik
fre 2002-11-08 klockan 09.21 skrev Schend, Thomas:
> Mhhh i red the squid.conf.default and found the acl but how can I apply them
> to all users?
>
> authenticate_ip_ttl 3600
> acl normal_users_max max_user_ip -s 1
>
> deny_info ERR_NO_DOUBLE_LOGIN dlogin_error
>
> http_access deny all normal_users_max dlogin_error
>
> Is this correct to apply this to all users? And how can I execlude a few
> users with a sceond rule?
>
> Can I do a hot exchange from squid 2.4 STABLE 6 to 2.5 STABLE 1?
> I am using Debian 3.0...
>
>
> -----Urspr�ngliche Nachricht-----
> Von: Henrik Nordstrom [mailto:hno@squid-cache.org]
> Gesendet: Freitag, 8. November 2002 08:32
> An: dumpmail@gmx.net
> Cc: Squid Users
> Betreff: Re: [squid-users] authenticate_ip_ttl_is_strict in ACL?
>
> In squid.conf.default after installing Squid-2.5, and in the release
> notes for Squid-2.5.
>
> Regards
> Henrik
>
> dumpmail@gmx.net wrote:
>
> > HN> You need to upgrade to Squid-2.5. There these things are ACL driven
> for
> > HN> greater flexibility on where and how the IP per user limitation should
> > HN> be applied. And as the check is now acl driven you can also use
> > HN> deny_info to assign custom error messages.
>
> > Where exactly is this documented ow how would such a ACL look like
> > (execluding + Custom Error Message).
> > Thansk for your Help!
> >
> > --
> > Thomas Schend
> > dumpmail@gmx.net mailto:dumpmail@gmx.net
Received on Mon Nov 11 2002 - 03:44:30 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:11:17 MST