Hi all,
I am currently struggling to turn mod_dav on. In theory, it is just Dav on,
but in practice I am getting a 405 Method Not Allowed in response to PROPFIND,
and nothing in the error_log to give a clue that anything is wrong.
So, before I go off and crank this up in a debugger to figure
Graham Leggett wrote:
I am currently struggling to turn mod_dav on. In theory, it is just
Dav on, but in practice I am getting a 405 Method Not Allowed
in response to PROPFIND
By any chance, are you using 2.4.x/trunk and do you have mod_dir
included in the build? I have a patch for a
On 31 Dec 2013, at 5:36 PM, Chris Darroch chr...@pearsoncmg.com wrote:
By any chance, are you using 2.4.x/trunk and do you have mod_dir
included in the build? I have a patch for a regression in 2.4.x/trunk
where mod_dir hijacks PROPFIND and triggers a 405. Try taking mod_dir
out and see
It looks like the issue is affecting me - I am using v2.4.7, and mod_dir is
present (but I can't turn it off without affecting other virtual hosts). It
seems to affect directories where a directoryindex is present. Do you have a
copy of the patch? If so I can test it and confirm the problem
Am Montag, 30. Dezember 2013, 16:48:51 schrieb Graham Leggett:
I am currently struggling to turn mod_dav on. In theory, it is just
Dav on, but in practice I am getting a 405 Method Not Allowed in
response to PROPFIND, and nothing in the error_log to give a clue
that anything is wrong.
Having
On 30 Dec 2013, at 6:14 PM, Eric Covener cove...@gmail.com wrote:
there is also a PR potentially in the same neighborhood:
https://issues.apache.org/bugzilla/show_bug.cgi?id=53929
For a while I thought it was a remove DefaultType issue in 2.4.x but
I think that is probably wrong.
A quick
Am Montag, 30. Dezember 2013, 19:04:53 schrieb Graham Leggett:
The first is there is no way to switch mod_dir off - you add the
module that means on. If you need the module on in one virtual
host, but off in another you're stuffed.
Doesn't DirectoryIndex disabled do the trick?
Graham Leggett wrote:
The second is that the module seems to want to respond to all methods,
GET, POST, PROPFIND, etc when in theory it should only respond to GET.
Yes, exactly. The history here seems to be due to a change made for
PR 25435, which made it into 2.4.x but was vetoed for
