httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 41449] - DAVGenericLockDB not allowed in main server configuration
Date Mon, 26 Feb 2007 19:06:35 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=41449>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=41449





------- Additional Comments From basant.kukreja@sun.com  2007-02-26 11:06 -------
If backend lock provider provides support of multiple lockdb then in my opinion,
DAVGenericLockDB must appear in <Directory> container. In that case this is a
invalid bug.

<Directory /x>
...
DavGenericLockDB var/DAVLock1
..
</Directory>

<Directory /x>
...
DavGenericLockDB var/DAVLock2
..
</Directory>

If the backend provider only supports a single lock db then it make sense to
make it a "Main configuration" directive.

As a safe option, it is made as a directive to be used in Directory container.

So I think we can mark this bug as "Invalid" bug.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message