Bug 1022520 - WebDAV - httpd.conf typo
Summary: WebDAV - httpd.conf typo
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss Enterprise Web Server 2
Classification: JBoss
Component: httpd
Version: 2.0.1
Hardware: All
OS: Windows
unspecified
high
Target Milestone: ---
: ---
Assignee: Mladen Turk
QA Contact: Libor Fuka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-23 13:04 UTC by Libor Fuka
Modified: 2019-06-13 08:00 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously in JBoss Enterprise Web Server, the location of the WebDAV lock database was incorrect in the <filename>httpd.conf</filename> file used for the mod_dav_fs configuration on Solaris and Microsoft Windows. In JBoss Enterprise Web Server 2.1, the incorrect <command>DAVLockDB var/run/lockdb</command> part of the configuration is now corrected to <command>DAVLockDB run/lockdb</command> and now works as expected.
Clone Of:
Environment:
Last Closed: 2019-06-13 08:00:10 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Libor Fuka 2013-10-23 13:04:37 UTC
Description of problem:
httpd.conf typo for Solaris and Windows for mod_dav_fs configuration:
<IfModule mod_dav_fs.c>
    # Location of the WebDAV lock database.
    DAVLockDB var/run/lockdb
</IfModule>
This should needs to be changed to:
<IfModule mod_dav_fs.c>
    # Location of the WebDAV lock database.
    DAVLockDB run/lockdb
</IfModule> 

Version-Release number of selected component (if applicable):
2.0.1 - Solaris and Windows

If its set to var/run/lockdb using mod_dav shows these errors in httpd error_log:
[Wed Oct 23 07:47:35 2013] [error] [client 127.0.0.1] Could not MOVE/COPY /davTest/hello.txt due to a failed precondition on the destination (e.g. locks).  [500, #0]
[Wed Oct 23 07:47:35 2013] [error] [client 127.0.0.1] The locks could not be queried for verification against a possible "If:" header.  [500, #0]
[Wed Oct 23 07:47:35 2013] [error] [client 127.0.0.1] Could not open the lock database.  [500, #400]
[Wed Oct 23 07:47:35 2013] [error] [client 127.0.0.1] (2)No such file or directory: Could not open property database.  [500, #1]

Comment 1 Jean-frederic Clere 2014-02-13 14:30:21 UTC
http://pkgs.devel.redhat.com/cgit/rpms/httpd/tree/httpd.conf?h=jb-ep-6-xb just needs a simple fix.

Comment 2 Libor Fuka 2014-04-29 14:36:11 UTC
Please fix this bug in EWS 2.1.0 ER1. Its simple fix.

Comment 3 Mladen Turk 2014-04-29 14:51:40 UTC
Fixed in the dist git.
EWS 2.1.0 will have run/lockdb

Comment 4 Libor Fuka 2014-04-29 15:07:58 UTC
Note: This fix should be only for Solaris and Windows build not for RHEL.

Comment 5 Mladen Turk 2014-04-29 15:50:20 UTC
Sure. I understood that. Fix was applied only to the multiplatform branch.

Comment 6 Libor Fuka 2014-06-11 12:38:03 UTC
Verified in EWS 2.1.0-ER2


Note You need to log in before you can comment on or make changes to this bug.