Bug 45379 - [Bug] svn merge, apache and trailing slashes
Summary: [Bug] svn merge, apache and trailing slashes
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_dav (show other bugs)
Version: 2.2.9
Hardware: Other Linux
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL: http://subversion.tigris.org/servlets...
Keywords: MassUpdate
Depends on:
Reported: 2008-07-11 06:21 UTC by Carsten Milkau
Modified: 2018-11-07 21:08 UTC (History)
0 users


Note You need to log in before you can comment on or make changes to this bug.
Description Carsten Milkau 2008-07-11 06:21:10 UTC
Subversion people claim this is a problem with apache:


Thanks for help!
Comment 1 Nick Kew 2008-07-11 09:26:25 UTC
I don't see anything resembling a bug report here.  If you're claiming an apache bug, please tell us what it is, and what's wrong about it.
Comment 2 Carsten Milkau 2008-07-11 10:14:42 UTC
The problem is described in the linked mailing list item (and its successors). I'll give a brief summary here again:

* Subversion uses DAV to implement its functionality in Apache.
* When using the svn merge command on a directory, subversion removes any trailing slash (if present)
* Apache replies with a 302 redirect to the same URL with a trailing slash
* Subversion treats the redirect answer as error

I asked subversion to include the trailing slash, however they answered mod_dav does not like trailing slashes. So it seems that mod_dav and some other part in apache don't agree on whether they want the URL with or without trailing slash.

Steps to reproduce:

* install recent versions of apache and subversion
* create a repository and a branch
* do an svn merge of a whole subtree (i.e. svn merge -rx:y http://localhost/svn/my_repository/some_directory my_working_copy_directory)
Comment 3 Ruediger Pluem 2008-07-11 14:49:09 UTC
Please try if setting redirect-carefully fixes your problem (http://httpd.apache.org/docs/2.2/env.html#special).

BrowserMatch "SVN/1\." redirect-carefully

should do the trick.
Comment 4 William A. Rowe Jr. 2018-11-07 21:08:36 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.