Recap,
1) .htaccess with a limit directive so:
<limit GET>
# a line commented out and nothing else...
</limit>
2) .htaccess protects a cgi-bin directory
3) access to protected scripts results in SIGSEGV
I've messed with 0.8.8 some more and it seems like this ONLY happens
when the .htaccess is in a cgi-bin area. Normally reachable (unaliased)
areads under DOCUMENT_ROOT which are protected by identical .htaccess
files are ok.
The only difference, in terms of accessing, is that the .htaccess file
sits in a part of the server for which a ScriptAlias has been defined
eg. srm.conf entries like:
ScriptAlias /cgi-bin/ /usr/local/etc/httpd/cgi-bin/
Is that at a big enough clue?
What's so special about script-aliased directories that gives 0.8.8
such a headache?
Ay.
1) .htaccess with a limit directive so:
<limit GET>
# a line commented out and nothing else...
</limit>
2) .htaccess protects a cgi-bin directory
3) access to protected scripts results in SIGSEGV
I've messed with 0.8.8 some more and it seems like this ONLY happens
when the .htaccess is in a cgi-bin area. Normally reachable (unaliased)
areads under DOCUMENT_ROOT which are protected by identical .htaccess
files are ok.
The only difference, in terms of accessing, is that the .htaccess file
sits in a part of the server for which a ScriptAlias has been defined
eg. srm.conf entries like:
ScriptAlias /cgi-bin/ /usr/local/etc/httpd/cgi-bin/
Is that at a big enough clue?
What's so special about script-aliased directories that gives 0.8.8
such a headache?
Ay.