On 2004-09-04 19:58:21 +0200, Stas Bekman <[EMAIL PROTECTED]> said:
The proper solution is :
Limit => {
'GET PUT POST DELETE PROPFIND PROPPATCH MKCOL COPY MOVE LOCK UNLOCK' => {
require => 'valid-user',
Order => 'allow,deny',
Allow => 'from all',
},
So it's not really a bug, more lack of documentation :)
Thanks to Rici Lake for handing this out to me...
-----
M.v.Buytene wrote:I am trying (as a starting test) to replace some apache directives by mod_perl's syntax, so i can hopefully easily yank in specific perl functions.
Running apache 2.0.50 Mod_perl 1.99
That's not enough information, Martijn. When reporting problems make sure to file a proper problem report: http://perl.apache.org/bugs/
Limit => { METHODS => 'GET POST', require => 'valid-user', Order => 'allow,deny', Allow => 'from all', }, }, };
When used with mod_perl i can enter the directory without authentication, and the same goes for webdav, no authentiction needed. Tho the vhost i created works like a charm.
What am i doing wrong?
Not sure why it doesn't work. Philippe? Tests?
but if you read: http://httpd.apache.org/docs-2.0/en/mod/core.html#limit it says:
Access controls are normally effective for all access methods, and this is the usual desired behavior. In the general case, access control directives should not be placed within a <Limit> section.
so try to drop the Limit block, till Philippe shows up.
-- __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
-- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
