[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Committing .htaccess files to a repository

From: Jan Hendrik <list.jan.hendrik_at_gmail.com>
Date: Mon, 9 Mar 2009 17:18:20 +0100

Concerning Committing .htaccess files to a rep
Thompson, Graeme (GE Infra, A wrote on 9 Mar 2009, 9:46, at least in part:

> Hi,
> We are running a SVN 1.5.2 served using Apache 2.2.10 running on
> openSUSE 11.1 and are having issues committing changes to .htaccess
> files.
> I am able to checkout quite happily using any protocol, however when I
> try to commit http://server/repos/project/folder/.htaccess we get:
> Commit failed (details follow):
> '/repos/project/!svn/wrk/ec1cffe3-4aba-b14c-a252-978250e0cd7c/folder/.
> ht access': Could not read status line: An existing connection was
> forcibly closed by the remote host.
> (http://server)
> I have tried committing using the file protocol with no problems and
> am therefore heading towards the belief that this is an issue with the
> apache server configuration.

Have you tried svn cleanup?

> The default apache configuration has the following lines in httpd.conf
> which seem to limit access to the .htaccess files:
> # forbid access to the entire filesystem by default
> <Directory />
> Options None
> AllowOverride None
> Order deny,allow
> Deny from all
> </Directory>
> # use .htaccess files for overriding,
> AccessFileName .htaccess

I should think that for this having any effect there should be a
relevant <Directory /> section with

AllowOverride [All or a combination from Options FileInfo
AuthConfig Limit]

for the folder you want to serve with Apache.

> # and never show them
> <Files ~ "^\.ht">
> Order allow,deny
> Deny from all
> </Files>
> However commenting these out, or changing the Deny to Allow does not
> seem to solve the problem.
> We are using the method recommended from the svn book to server the
> repository, from out subversion.conf:
> <Location /repos/Project>
> DAV svn
> LimitXMLRequestBody 0
> SVNPath /srv/svn/repos/Project
> # Limit write permission to list of valid users.
> AuthType Basic
> AuthName "Authorization Realm"
> AuthUserFile /srv/svn/user_access/project_passwdfile
> Require valid-user
> </Location>

Basically this is what we have, too.

But is the rejected .htaccess file in any way relevant to the
/srv/svn/repos/Project path? FWIW we have hundreds of .htaccess
files in our web projects and commit them w/o issues via Apache
2.0.63 (and earlier). The working copy folders have some
AllowOverride setting of course to allow for local testing, but as
siad this should have no bearing for SVN commits.

Freedom quote:

     What light is to the eyes - what air is to the lungs -
     what love is to the heart, liberty is to the soul of man.
               -- Robert Green Ingersoll


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-03-09 17:19:16 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.