Return-Path: Delivered-To: apmail-subversion-users-archive@minotaur.apache.org Received: (qmail 50482 invoked from network); 10 Mar 2011 01:08:38 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 10 Mar 2011 01:08:38 -0000 Received: (qmail 17185 invoked by uid 500); 10 Mar 2011 01:08:38 -0000 Delivered-To: apmail-subversion-users-archive@subversion.apache.org Received: (qmail 17168 invoked by uid 500); 10 Mar 2011 01:08:38 -0000 Mailing-List: contact users-help@subversion.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@subversion.apache.org Received: (qmail 17161 invoked by uid 99); 10 Mar 2011 01:08:38 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Mar 2011 01:08:38 +0000 X-ASF-Spam-Status: No, hits=0.7 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_HELO_PASS,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [80.67.31.98] (HELO smtprelay05.ispgateway.de) (80.67.31.98) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Mar 2011 01:08:29 +0000 Received: from [70.114.142.233] (helo=[192.168.1.5]) by smtprelay05.ispgateway.de with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.68) (envelope-from ) id 1PxUMK-000684-1f; Thu, 10 Mar 2011 02:08:08 +0100 Subject: Re: dav_svn enabled for one hostname only? Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=windows-1252 From: Ryan Schmidt In-Reply-To: Date: Wed, 9 Mar 2011 19:08:05 -0600 Cc: "users@subversion.apache.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Oliver Marshall X-Mailer: Apple Mail (2.1082) X-Df-Sender: 368818 X-Virus-Checked: Checked by ClamAV on apache.org On Mar 9, 2011, at 03:07, Oliver Marshall wrote: > Is it possible to enable the dav_svn module for one hostname only? Modules are *loaded* globally for an Apache instance, but the directives = to actually make use of a module can be limited by any number of means, = including hostname, as discussed further below. > We have a development box which was just being used for SVN. Then Trac = got added, then it started being used for hosting demo sites, then =85.. = etc. > =20 > We now have about 10 various hostnames on there and we have found if = you add /svn on to any of them you can access the SVN module. This isn=92t= a massive issue as it=92s password protected but only the SVN site = itself (dev.mydomain.com) is SSL enabled. This is a matter of where you use your "DAV svn" statement (the = statement that says "I want mod_dav_svn to start taking effect here"), = and yes, that should absolutely be restricted to only the area you want = it to be used in, for example a particular hostname. You probably have = "DAV svn" and all the other directives relating to serving your = repository(ies) sitting naked in the main part of your Apache httpd.conf = file: DAV svn ... And you should move them into a VirtualHost directive specific to the = hostname you want them to be used in, e.g.: ServerName dev.example.com DAV svn ... You may already have a VirtualHost directive for this hostname; in that = case, don't add a second one, but merge these directives into the = existing one.