[ 
https://issues.apache.org/jira/browse/SVN-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ivan Zhakov resolved SVN-1934.
------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: unscheduled)
                   1.7.0

The issue seems to be fixed long-time ago: I'm getting proper URLs with 
Subversion 1.7.0, 1.8.0 and 1.9.0:
{noformat}
"OPTIONS /trunk HTTP/1.1" 401 401
"OPTIONS /trunk HTTP/1.1" 401 401
"OPTIONS /trunk HTTP/1.1" 200 179
"PROPFIND /trunk HTTP/1.1" 207 668
"MKACTIVITY /!svn/act/1f318d77-8b7b-104f-94b1-1565cdd07d38 HTTP/1.1" 201 218
"PROPFIND /trunk HTTP/1.1" 207 379
"CHECKOUT /!svn/vcc/default HTTP/1.1" 201 235
"PROPPATCH /!svn/wbl/1f318d77-8b7b-104f-94b1-1565cdd07d38/2033 HTTP/1.1" 207 511
"PROPFIND /!svn/vcc/default HTTP/1.1" 207 440
"PROPFIND /!svn/bc/2033/trunk HTTP/1.1" 207 392
"CHECKOUT /!svn/ver/2033/trunk/README HTTP/1.1" 201 243
"PUT /!svn/wrk/1f318d77-8b7b-104f-94b1-1565cdd07d38/trunk/README HTTP/1.1" 204 -
"MERGE /trunk HTTP/1.1" 200 701
"DELETE /!svn/act/1f318d77-8b7b-104f-94b1-1565cdd07d38 HTTP/1.1" 204 -
{noformat}

Resolving as Fixed.

> When repository is in root '/', URL construction is questionably valid
> ----------------------------------------------------------------------
>
>                 Key: SVN-1934
>                 URL: https://issues.apache.org/jira/browse/SVN-1934
>             Project: Subversion
>          Issue Type: Bug
>          Components: mod_dav_svn
>    Affects Versions: all
>         Environment: FreeBSD
>            Reporter: Subversion Importer
>             Fix For: 1.7.0
>
>
> {noformat:nopanel=true}
> With a Repos configured to the root ('/') of Apache, commits could not 
> complete
> with 1.0.5.  This is a regression from 0.37.0.  
> Apache Configuration:
> <Location "/">
>   SetOutputFilter DEFLATE
>   DAV svn
>   SVNPath /home/svn/repos
>   AuthType Basic
>   AuthName "Carroll College Subversion repository"
>   AuthBasicProvider file
>   AuthUserFile /home/svn/svn_authentication
>   Require valid-user
> </Location>
> With This exact same configuration with subversion 0.37.0, it worked perfectly
> fine.  After upgrading to 1.0.5, checkouts and updates worked fine, but any
> commits with fail with:
> svn: applying log message to
> //!svn/wbl/dafd7a36-77dd-0310-8dd8-f106bb595ebe/1658: 404 Not Found (....)
> The problem is, after the client does 'CHECKOUT /!svn/bln/1658 HTTP/1.1', the
> server replies with a 'Location:
> http://www-dev.carroll.edu:8080//!svn/wbl/d7d1dd50-77dd-0310-a09d-81329e6f7133/1658'
> in the 201 Created message.  It seems like the server is the one telling the
> client the incorrect URL.
> The next message from the client would be a 'PROPPATCH
> //!svn/wbl/d7d1dd50-77dd-0310-a09d-81329e6f7133/1658 HTTP/1.1', which the 
> server
> would return as a 404 and break the commit.
> As a workaround, I moved the repository from '/' to '/svn' and it now works
> correctly.  It seems that there is a regression in Subversion between 0.37.0 
> and
> 1.0.5 when your repository is in the root directory of Apache.
> {noformat}
> Original issue reported by *chipig*



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to