Return-Path: Delivered-To: apmail-httpd-users-archive@www.apache.org Received: (qmail 10679 invoked from network); 25 Oct 2010 13:20:32 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 25 Oct 2010 13:20:32 -0000 Received: (qmail 74487 invoked by uid 500); 25 Oct 2010 13:20:28 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 74333 invoked by uid 500); 25 Oct 2010 13:20:24 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 74325 invoked by uid 99); 25 Oct 2010 13:20:23 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Oct 2010 13:20:23 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [84.12.148.82] (HELO igw2.ssl.co.uk) (84.12.148.82) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Oct 2010 13:20:17 +0000 Received: from windy.internal (windy.internal [172.25.0.122]) by igw2.ssl.co.uk (8.14.4/8.14.4) with ESMTP id o9PDJt7m030068 for ; Mon, 25 Oct 2010 14:19:55 +0100 Received: from [172.25.0.201] (sachadell [172.25.0.201]) by windy.internal (8.14.1/8.14.1) with ESMTP id o9PDJtXb009808 for ; Mon, 25 Oct 2010 14:19:55 +0100 Message-ID: <4CC582D2.3080201@ssl.co.uk> Date: Mon, 25 Oct 2010 14:14:58 +0100 From: Sacha Varma User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.11) Gecko/20101013 Thunderbird/3.1.5 MIME-Version: 1.0 To: users@httpd.apache.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [users@httpd] Basic authentication for a virtual/rewritten URL? 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 authentication directives are only valid in Directory and htacces contexts, so I'm not able to password-protect a Location. On a filthy hunch I tried creating the directory in the filesystem that would correspond to the URL, and password-protecting that via a Directory configuration block, but that didn't work. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See for more info. To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org " from the digest: users-digest-unsubscribe@httpd.apache.org For additional commands, e-mail: users-help@httpd.apache.org