Bug 55590 - second commit is failing if space is in file name or file path
Summary: second commit is failing if space is in file name or file path
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: All (show other bugs)
Version: 2.2.25
Hardware: PC All
: P1 major (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
Keywords: MassUpdate
Depends on:
Reported: 2013-09-24 15:24 UTC by kesavan
Modified: 2018-11-07 21:09 UTC (History)
0 users


Note You need to log in before you can comment on or make changes to this bug.
Description kesavan 2013-09-24 15:24:26 UTC
The issue with Apache 2.2.25 is when you have ‘space’ in folder name / file name. The first commit of these files / folders (with space in the name) is successful. We are facing issue only when subsequent commit is happening. We are using Tortoise SVN as client.
Comment 1 Eric Covener 2013-09-24 15:51:52 UTC
Why do you think this is an issue in Apache vs. some plugin you've added to handle subversion? You'll have to provide a lot more detail.

Comment 2 kesavan 2013-09-24 16:12:38 UTC
We are using Subversion (SVN 1.6.12-r955802) for this repo. This subversion and the modules (dav_svn_module & authz_svn_module) provided by it, are working fine with previous Apache version 2.2.24.

Since the Apache version 2.2.24 has some security issues (multi-site secutity issue), we have moved to Apache version 2.2.25. But this updated version has the second commit issue.

We are almost blocked to use the Apache.

Kindly provide us some workaround and hotfix for this issue.
Comment 3 Eric Covener 2014-01-19 23:40:41 UTC
report back if 2.2.26 doesn't fix it, PR55397.
Comment 4 William A. Rowe Jr. 2018-11-07 21:09:41 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.