Re: [us...@httpd] Basic authentication for a virtual/rewritten URL?

2010-10-27 Thread Sacha Varma
ame "Restricted Directory" AuthUserFile /some/where/user.pass Require user someuser On Oct 26, 2010, at 9:55 AM, Sacha Varma wrote: On 19:59, Brian Hirt wrote: Use instead of That's the first thing I tried, and was surpr

Re: [us...@httpd] Basic authentication for a virtual/rewritten URL?

2010-10-26 Thread Sacha Varma
On 19:59, Brian Hirt wrote: Use instead of That's the first thing I tried, and was surprised when it didn't work. The documentation is explicit though, the only valid contexts for the mod_auth directives are Directory and htaccess: http://httpd.apache.org/docs/2.0/mod/mod_auth.html Do

[us...@httpd] Basic authentication for a virtual/rewritten URL?

2010-10-25 Thread Sacha Varma
Sorry to interrupt you fine folks, I wasn't able to google up the answer to this. Is it possible to configure Apache to do basic authentication for a URL that doesn't correspond to a physical location in the filesystem (e.g. because it is rewritten to be served by CGI)? It appears that the a

[us...@httpd] RewriteMap & hashes: dealing with a hash miss

2009-02-06 Thread Sacha Varma
(In the course of writing this e-mail I worked out the answer, but I thought I'd post it anyway, for future hapless rewriters such as myself.) I have a website whose URLs often include an identifier for the underlying database record that powers the page. Simplified example for illustra

[us...@httpd] Serving default error pages after CGI?

2009-01-13 Thread Sacha Varma
I've been unable to google up the answer to this, so if anyone can help it would be much appreciated. The CGI standard (RFC 3875, 6.3.3) allows a CGI script to output an HTTP status code header (e.g. 'Status: 404 Not Found'). A response body is optional. My CGI program outputs just this stat