- "Sacha Varma" wrote:
> Ok, thanks Brian.
>
> For the log - after a bit of experimentation, the problem I have
> appears
> to be that while you can password-protect a Location, Location
> directives are applied after rewrites. So if you have:
>
> ScriptAlias /cgi-bin/ /some/where/c
Ok, thanks Brian.
For the log - after a bit of experimentation, the problem I have appears
to be that while you can password-protect a Location, Location
directives are applied after rewrites. So if you have:
ScriptAlias /cgi-bin/ /some/where/cgi-bin/
RewriteRule ^.*$ /cgi-bin/my-cms
I don't use htaccess anywhere, but we use things like this in our config that
work just fine. You might want to make sure your Order and Allow are set up to
work correctly.
AuthType Basic
AuthName "Restricted Directory"
AuthUserFile
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
Use instead of
Brian Hirt
bh...@me.com
On Oct 25, 2010, at 7:14 AM, Sacha Varma wrote:
> 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
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
