You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by "Thompson, Graeme (GE Infra, Aviation)" <Gr...@ge.com> on 2009/03/09 13:46:14 UTC
Committing .htaccess files to a repository
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):
PROPFIND of
'/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.
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
# 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>
Does anyone have any ideas or suggestions?
Thank you,
Graeme
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1296244
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: Committing .htaccess files to a repository
Posted by Jan Hendrik <li...@gmail.com>.
Concerning Re: Committing .htaccess files to a
Fernando Favini wrote on 13 Mar 2009, 8:45, at least in part:
> I never used apache with SVN, but i would think that the issue is
> something like apache forbiding you to reach .htaccess files.
Yes, when *accessing* files on a webserver default Apache setting
is to forbid access to .ht* files. Yet for committing into an SVN
repos Apache *should* never care as that's the business of SVN
on both ends of the line while Apache just acts as the messenger.
Or so I see it at least. Obviously it does interfere in Graeme's
setup, however.
> I run svn to save the changes on my web site, but i always comit using
> svn:// or file:// protocol and i can store .ht files wit success
>
> On Thu, Mar 12, 2009 at 1:29 PM, Jan Hendrik
> <li...@gmail.com>wrote:
Not that it would be any kind of essential in this case except for
some irritation perhaps, but please keep the quoting in order; I
didn't write the following line, I just forwarded Graeme Thompson's
message back to the list. -- JH
> > Thank you for your reply, I have responded inline...
> >
> > > -----Original Message-----
> > > From: Jan Hendrik [mailto:list.jan.hendrik@gmail.com]
> > > Sent: 09 March 2009 16:18
> > > To: users@subversion.tigris.org
> > > Subject: Re: Committing .htaccess files to a repository
> > >
> > > 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):
> > > > PROPFIND of
> > > >
> > > '/repos/project/!svn/wrk/ec1cffe3-4aba-b14c-a252-978250e0cd7c/fold
> > > er/.
> > > > 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?
> > >
> > I have just tried it with a completely fresh repository, clean
> > checkout and only adding a single .htaccess file, and this still
> > fails.
> >
> > > > 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.
> >
> > I would agree with that.
> >
> > >
> > > > # 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.
> >
> >
> > Here are the apache access log entries when trying to commit:
> >
> > X.x.x.x - - [12/Mar/2009:16:00:34 +0000] "OPTIONS /repos/test
> > HTTP/1.1" 401 1252 "-" "SVN/1.5.1 (r32289) neon/0.28.2" X.x.x.x -
> > gct [12/Mar/2009:16:00:34 +0000] "OPTIONS /repos/test HTTP/1.1" 200
> > - "-" "SVN/1.5.1 (r32289) neon/0.28.2" X.x.x.x - gct
> > [12/Mar/2009:16:00:34 +0000] "PROPFIND /repos/test HTTP/1.1" 207 651
> > "-" "SVN/1.5.1 (r32289) neon/0.28.2" X.x.x.x - gct
> > [12/Mar/2009:16:00:34 +0000] "OPTIONS /repos/test HTTP/1.1" 200 190
> > "-" "SVN/1.5.1 (r32289) neon/0.28.2" X.x.x.x - gct
> > [12/Mar/2009:16:00:34 +0000] "MKACTIVITY
> > /repos/test/!svn/act/bb48ac16-664e-c648-adf7-e787951a0a9f HTTP/1.1"
> > 201 309 "-" "SVN/1.5.1 (r32289) neon/0.28.2" X.x.x.x - gct
> > [12/Mar/2009:16:00:34 +0000] "PROPFIND /repos/test/!svn/vcc/default
> > HTTP/1.1" 207 402 "-" "SVN/1.5.1 (r32289) neon/0.28.2" X.x.x.x - gct
> > [12/Mar/2009:16:00:34 +0000] "CHECKOUT /repos/test/!svn/bln/0
> > HTTP/1.1" 201 323 "-" "SVN/1.5.1 (r32289) neon/0.28.2" X.x.x.x - gct
> > [12/Mar/2009:16:00:34 +0000] "PROPPATCH
> > /repos/test/!svn/wbl/bb48ac16-664e-c648-adf7-e787951a0a9f/0
> > HTTP/1.1" 207 462 "-" "SVN/1.5.1 (r32289) neon/0.28.2" X.x.x.x - gct
> > [12/Mar/2009:16:00:34 +0000] "PROPFIND /repos/test HTTP/1.1" 207 387
> > "-" "SVN/1.5.1 (r32289) neon/0.28.2" X.x.x.x - gct
> > [12/Mar/2009:16:00:34 +0000] "CHECKOUT /repos/test/!svn/ver/0/
> > HTTP/1.1" 201 322 "-" "SVN/1.5.1 (r32289) neon/0.28.2" X.x.x.x - -
> > [12/Mar/2009:16:00:34 +0000] "PROPFIND
> > /repos/test/!svn/wrk/bb48ac16-664e-c648-adf7-e787951a0a9f/.htaccess
> > HTTP/1.1" 404 1015 "-" "SVN/1.5.1 (r32289) neon/0.28.2" X.x.x.x - -
> > [12/Mar/2009:16:00:36 +0000] "PROPFIND
> > /repos/test/!svn/wrk/bb48ac16-664e-c648-adf7-e787951a0a9f/.htaccess
> > HTTP/1.1" 404 1015 "-" "SVN/1.5.1 (r32289) neon/0.28.2" X.x.x.x -
> > gct [12/Mar/2009:16:00:37 +0000] "DELETE
> > /repos/test/!svn/act/bb48ac16-664e-c648-adf7-e787951a0a9f HTTP/1.1"
> > 204 - "-" "SVN/1.5.1 (r32289) neon/0.28.2"
> >
> >
> > svnserve access works perfectly, File access also works perfectly
> > and I can checkout perfectly with all 3 protocols, including http.
> >
> > The only thing that is failing is the committing of .htaccess files
> > with the error of the connection being forcible closed.
> >
> > Is anyone else running happily on the Apache 2.2.10 and Subversion
> > 1.5.2 server that are provided by default with openSUSE 11.1?
> >
> > Graeme
> >
> > ------------------------------------------------------
> >
> > http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMess
> > ageId=1316854
> >
> > To unsubscribe from this discussion, e-mail: [
> > users-unsubscribe@subversion.tigris.org].
> >
>
>
>
> --
>
> Simone de Beauvoir - "To catch a husband is an art; to hold him is a
> job."
>
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessag
> eId=1317042
>
> To unsubscribe from this discussion, e-mail:
> [users-unsubscribe@subversion.tigris.org].
---------------------------------------
Freedom quote:
"Liberty's too precious a thing to be buried in books, Miss Saunders.
Men should hold it up in front of them every single day of their lives
and say: 'I'm free to think and to speak. My ancestors couldn't.
I can. And my children will.'"
-- James Stewart as Jefferson Smith
in "Mr. Smith goes to Washington" by Frank Capra, 1939
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1317108
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: Committing .htaccess files to a repository
Posted by Fernando Favini <da...@gmail.com>.
I never used apache with SVN, but i would think that the issue is something
like apache forbiding you to reach .htaccess files.
I run svn to save the changes on my web site, but i always comit using
svn:// or file:// protocol and i can store .ht files wit success
On Thu, Mar 12, 2009 at 1:29 PM, Jan Hendrik <li...@gmail.com>wrote:
> Thank you for your reply, I have responded inline...
>
> > -----Original Message-----
> > From: Jan Hendrik [mailto:list.jan.hendrik@gmail.com]
> > Sent: 09 March 2009 16:18
> > To: users@subversion.tigris.org
> > Subject: Re: Committing .htaccess files to a repository
> >
> > 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):
> > > PROPFIND of
> > >
> > '/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?
> >
> I have just tried it with a completely fresh repository, clean checkout
> and only adding a single .htaccess file, and this still fails.
>
> > > 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.
>
> I would agree with that.
>
> >
> > > # 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.
>
>
> Here are the apache access log entries when trying to commit:
>
> X.x.x.x - - [12/Mar/2009:16:00:34 +0000] "OPTIONS /repos/test HTTP/1.1"
> 401 1252 "-" "SVN/1.5.1 (r32289) neon/0.28.2"
> X.x.x.x - gct [12/Mar/2009:16:00:34 +0000] "OPTIONS /repos/test
> HTTP/1.1" 200 - "-" "SVN/1.5.1 (r32289) neon/0.28.2"
> X.x.x.x - gct [12/Mar/2009:16:00:34 +0000] "PROPFIND /repos/test
> HTTP/1.1" 207 651 "-" "SVN/1.5.1 (r32289) neon/0.28.2"
> X.x.x.x - gct [12/Mar/2009:16:00:34 +0000] "OPTIONS /repos/test
> HTTP/1.1" 200 190 "-" "SVN/1.5.1 (r32289) neon/0.28.2"
> X.x.x.x - gct [12/Mar/2009:16:00:34 +0000] "MKACTIVITY
> /repos/test/!svn/act/bb48ac16-664e-c648-adf7-e787951a0a9f HTTP/1.1" 201
> 309 "-" "SVN/1.5.1 (r32289) neon/0.28.2"
> X.x.x.x - gct [12/Mar/2009:16:00:34 +0000] "PROPFIND
> /repos/test/!svn/vcc/default HTTP/1.1" 207 402 "-" "SVN/1.5.1 (r32289)
> neon/0.28.2"
> X.x.x.x - gct [12/Mar/2009:16:00:34 +0000] "CHECKOUT
> /repos/test/!svn/bln/0 HTTP/1.1" 201 323 "-" "SVN/1.5.1 (r32289)
> neon/0.28.2"
> X.x.x.x - gct [12/Mar/2009:16:00:34 +0000] "PROPPATCH
> /repos/test/!svn/wbl/bb48ac16-664e-c648-adf7-e787951a0a9f/0 HTTP/1.1"
> 207 462 "-" "SVN/1.5.1 (r32289) neon/0.28.2"
> X.x.x.x - gct [12/Mar/2009:16:00:34 +0000] "PROPFIND /repos/test
> HTTP/1.1" 207 387 "-" "SVN/1.5.1 (r32289) neon/0.28.2"
> X.x.x.x - gct [12/Mar/2009:16:00:34 +0000] "CHECKOUT
> /repos/test/!svn/ver/0/ HTTP/1.1" 201 322 "-" "SVN/1.5.1 (r32289)
> neon/0.28.2"
> X.x.x.x - - [12/Mar/2009:16:00:34 +0000] "PROPFIND
> /repos/test/!svn/wrk/bb48ac16-664e-c648-adf7-e787951a0a9f/.htaccess
> HTTP/1.1" 404 1015 "-" "SVN/1.5.1 (r32289) neon/0.28.2"
> X.x.x.x - - [12/Mar/2009:16:00:36 +0000] "PROPFIND
> /repos/test/!svn/wrk/bb48ac16-664e-c648-adf7-e787951a0a9f/.htaccess
> HTTP/1.1" 404 1015 "-" "SVN/1.5.1 (r32289) neon/0.28.2"
> X.x.x.x - gct [12/Mar/2009:16:00:37 +0000] "DELETE
> /repos/test/!svn/act/bb48ac16-664e-c648-adf7-e787951a0a9f HTTP/1.1" 204
> - "-" "SVN/1.5.1 (r32289) neon/0.28.2"
>
>
> svnserve access works perfectly, File access also works perfectly and I
> can checkout perfectly with all 3 protocols, including http.
>
> The only thing that is failing is the committing of .htaccess files with
> the error of the connection being forcible closed.
>
> Is anyone else running happily on the Apache 2.2.10 and Subversion 1.5.2
> server that are provided by default with openSUSE 11.1?
>
> Graeme
>
> ------------------------------------------------------
>
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1316854
>
> To unsubscribe from this discussion, e-mail: [
> users-unsubscribe@subversion.tigris.org].
>
--
Simone de Beauvoir - "To catch a husband is an art; to hold him is a job."
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1317042
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
RE: Committing .htaccess files to a repository
Posted by Jan Hendrik <li...@gmail.com>.
Thank you for your reply, I have responded inline...
> -----Original Message-----
> From: Jan Hendrik [mailto:list.jan.hendrik@gmail.com]
> Sent: 09 March 2009 16:18
> To: users@subversion.tigris.org
> Subject: Re: Committing .htaccess files to a repository
>
> 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):
> > PROPFIND of
> >
> '/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?
>
I have just tried it with a completely fresh repository, clean checkout
and only adding a single .htaccess file, and this still fails.
> > 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.
I would agree with that.
>
> > # 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.
Here are the apache access log entries when trying to commit:
X.x.x.x - - [12/Mar/2009:16:00:34 +0000] "OPTIONS /repos/test HTTP/1.1"
401 1252 "-" "SVN/1.5.1 (r32289) neon/0.28.2"
X.x.x.x - gct [12/Mar/2009:16:00:34 +0000] "OPTIONS /repos/test
HTTP/1.1" 200 - "-" "SVN/1.5.1 (r32289) neon/0.28.2"
X.x.x.x - gct [12/Mar/2009:16:00:34 +0000] "PROPFIND /repos/test
HTTP/1.1" 207 651 "-" "SVN/1.5.1 (r32289) neon/0.28.2"
X.x.x.x - gct [12/Mar/2009:16:00:34 +0000] "OPTIONS /repos/test
HTTP/1.1" 200 190 "-" "SVN/1.5.1 (r32289) neon/0.28.2"
X.x.x.x - gct [12/Mar/2009:16:00:34 +0000] "MKACTIVITY
/repos/test/!svn/act/bb48ac16-664e-c648-adf7-e787951a0a9f HTTP/1.1" 201
309 "-" "SVN/1.5.1 (r32289) neon/0.28.2"
X.x.x.x - gct [12/Mar/2009:16:00:34 +0000] "PROPFIND
/repos/test/!svn/vcc/default HTTP/1.1" 207 402 "-" "SVN/1.5.1 (r32289)
neon/0.28.2"
X.x.x.x - gct [12/Mar/2009:16:00:34 +0000] "CHECKOUT
/repos/test/!svn/bln/0 HTTP/1.1" 201 323 "-" "SVN/1.5.1 (r32289)
neon/0.28.2"
X.x.x.x - gct [12/Mar/2009:16:00:34 +0000] "PROPPATCH
/repos/test/!svn/wbl/bb48ac16-664e-c648-adf7-e787951a0a9f/0 HTTP/1.1"
207 462 "-" "SVN/1.5.1 (r32289) neon/0.28.2"
X.x.x.x - gct [12/Mar/2009:16:00:34 +0000] "PROPFIND /repos/test
HTTP/1.1" 207 387 "-" "SVN/1.5.1 (r32289) neon/0.28.2"
X.x.x.x - gct [12/Mar/2009:16:00:34 +0000] "CHECKOUT
/repos/test/!svn/ver/0/ HTTP/1.1" 201 322 "-" "SVN/1.5.1 (r32289)
neon/0.28.2"
X.x.x.x - - [12/Mar/2009:16:00:34 +0000] "PROPFIND
/repos/test/!svn/wrk/bb48ac16-664e-c648-adf7-e787951a0a9f/.htaccess
HTTP/1.1" 404 1015 "-" "SVN/1.5.1 (r32289) neon/0.28.2"
X.x.x.x - - [12/Mar/2009:16:00:36 +0000] "PROPFIND
/repos/test/!svn/wrk/bb48ac16-664e-c648-adf7-e787951a0a9f/.htaccess
HTTP/1.1" 404 1015 "-" "SVN/1.5.1 (r32289) neon/0.28.2"
X.x.x.x - gct [12/Mar/2009:16:00:37 +0000] "DELETE
/repos/test/!svn/act/bb48ac16-664e-c648-adf7-e787951a0a9f HTTP/1.1" 204
- "-" "SVN/1.5.1 (r32289) neon/0.28.2"
svnserve access works perfectly, File access also works perfectly and I
can checkout perfectly with all 3 protocols, including http.
The only thing that is failing is the committing of .htaccess files with
the error of the connection being forcible closed.
Is anyone else running happily on the Apache 2.2.10 and Subversion 1.5.2
server that are provided by default with openSUSE 11.1?
Graeme
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1316854
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: Committing .htaccess files to a repository
Posted by Jan Hendrik <li...@gmail.com>.
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):
> PROPFIND of
> '/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.
JH
---------------------------------------
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
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1297468
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].