Re: [us...@httpd] allow autoindex for a directory, but not for its subdirectories

Freek Dijkstra wrote: > Again, I really still don't understand the purpose of the AP_REG_NOTEOL > flag. [...] The > more I think about it, the less sense it makes. Here is the history: r76312 (1996-01-14) src/main/http_request.c, initial revision if (is_matchexp(entry_dir) &a

Re: [us...@httpd] allow autoindex for a directory, but not for its subdirectories

Eric Covener wrote: > I didn't realize that was an option, or that it would help matters. I am not sure if it does helps; Frankly, this is the first time I look at the Apache code. I still don't understand how things relate, so the above contains a few assumptions. Take it as a suggestion how I w

Re: [us...@httpd] allow autoindex for a directory, but not for its subdirectories

Freek Dijkstra wrote: > Steps to reproduce > 1. Add the following configuration to httpd.conf: > > Alias /test/ /var/www/test/ > > > Options Indexes > Order deny,allow > Deny from all > > > > Allow from all > > > > Exp

Re: [us...@httpd] allow autoindex for a directory, but not for its subdirectories

Eric Covener wrote: > The patch is very easy, but I am afraid it might not be suitable to > backport to 2.2.x. > > I struggled with finding some fancy PCRE feature that would make this > work as most people expect it to -- \Z or negative lookahead, but > AFAICT they all fail to simulate the $ due

Re: [us...@httpd] allow autoindex for a directory, but not for its subdirectories

Eric Covener wrote: > https://issues.apache.org/bugzilla/show_bug.cgi?id=49809 > > I had looked into this august 2009 and couldn't figure out any good > reason why it should be matched as a literal. Eric, Thanks for looking into this. It is highly appreciated. Is there anything I can do to help?

Re: [us...@httpd] allow autoindex for a directory, but not for its subdirectories

[My apologies for the many posts; I just notices that my mailer removed the thinking it was HTML] Freek Dijkstra wrote: > Curious, > is never matched > is matched. > Logically, I would have expected both regexps to yield the same result. I did some more testing, and it just se

Re: [us...@httpd] Conundrum

James Coyle wrote: > Ever since I reinstalled Snow Leopard on my Mac, i've had some serious > Apache issues. Judging from this diagnostic information: > >> httpd: Syntax error on line 54 of /private/etc/apache2/httpd.conf: >> Cannot load /private/etc/apache2/libexec/apache2/mod_authn_file.so >> int

Re: [us...@httpd] allow autoindex for a directory, but not for its subdirectories

Freek Dijkstra wrote: > Curious, > is never matched > is matched. > Logically, I would have expected both regexps to yield the same result. I did some more testing, and it just seems that the the end of line anchor is just never matched. I can easily reproduce it with only a few c

Re: [us...@httpd] allow autoindex for a directory, but not for its subdirectories

Freek Dijkstra wrote: It seems that is just not matched for some reason. Curious, is not matched either However, is matched. Logically, I would have expected both regexps to yield the same result. Freek - The official

Re: [us...@httpd] allow autoindex for a directory, but not for its subdirectories

Eric Covener wrote: Allow from all satisfy any? Sorry, no change. Requesting /projects/ still gives a 403 Forbidden. Also, If I understand correctly, what I want is "satisfy all"; (thus both require valid-user and allow all should be satisfied.) It seems that is just not matched for

[us...@httpd] allow autoindex for a directory, but not for its subdirectories

of subdirectories, which is not what I want. I also tried and "^/projects/$">, but that all gives a 403 Forbidden. I have the feelings I'm missing something obvious here. I'm using Apache 2.2.9 on Debian Lenny. How