mod_auth_useragent allows you to forbid clients based on their
User-Agent by placing a single line in your Apache httpd.conf. Be aware
that this is by no means a security measure as it is trivial to change
your User-Agent in most browsers.
- Set EXPIRATION_DATE to an actual date (9.0 is behind, so guess 2 months from
now).
- This can be changed later as needed, if at all, either way we won't remove
them
until after 9.0 is released.
With Hat: apache@
Reported by: dvl via freshports
----------------------------------------------------------------------
ports/www/mod_accesscookie/distinfo CVS:
ports/www/mod_access_referer/distinfo CVS:
ports/www/mod_access_identd/distinfo CVS:
ports/www/mod_auth_cookie_mysql/distinfo CVS:
ports/www/mod_auth_imap/distinfo CVS:
ports/www/mod_auth_useragent/distinfo CVS: ports/www/mod_curb/distinfo
ports/www/mod_macro/distinfo CVS:
----------------------------------------------------------------------
Force commit to note that those ports has also been SHA256'ified
- prepare removal of www/apache2 in favor of www/apache20 for naming
consistency
- add entries in UPDATING (for apache22 too)
PR: ports/78119
Repocopied by: marcus
Add mod_auth_useragent 1.0
mod_auth_useragent allows you to forbid clients based on their
User-Agent by placing a single line in your Apache httpd.conf. Be aware
that this is by no means a security measure as it is trivial to change
your User-Agent in most browsers.
WWW: http://tangent.org/index.pl?lastnode_id=478&node_id=423