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 Thu, 22 Feb 2007 07:58:45 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 Bjorn.Wiberg@its.uu.se  2007-02-21 23:58 -------
Hello!

Currently we are not utilizing the generic lock DB at all -- I included it in
the configuration for completeness.

I see that the documentation
(http://httpd.apache.org/docs/2.2/mod/mod_dav_lock.html) states that "without a
backend provider which makes use of it, it's useless and should not be loaded
into the server", so I'll leave it commented out for now.

However, the same documentation
(http://httpd.apache.org/docs/2.2/mod/mod_dav_lock.html#davgenericlockdb) states
"Context: server config ...", so from that, it appears that it should be
available to use in the main server configuration. I see no reason for not
allowing it there, though (the lock database ought to be able to be shared
between all modules needing it, and for all vhosts, in one go?).

Best regards,
Björn

-- 
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