Subject: Re: [[email protected]] Strange WebDAV behavior on MKCOL
for 1 client only
Try mod_dumpio or a packet capture to see what else is different about the request.
On Mon, Aug 7, 2017 at 3:53 PM, Todd Blum <[email protected]
I have Apache mod_dav running on Windows 2012.
When a webDAV enabled application connects and tries to MKCOL on a directory that already exists, it receives an HTTP 400:
yyy.yyy.yyy.yy - username [07/Aug/2017:11:00:03 -0700] "MKCOL /webdav/dir1/dir2/dir3/dir4/dir5/dir6/ HTTP/1.1" 400 226____________________________________________________________________________
However, all other clients are receiving an HTTP 405 when they issue a MKCOL for a directory that already exists:
xxx.xxx.xxx.xx - username [07/Aug/2017:12:32:16 -0700] "MKCOL /webdav/dir1/dir2/dir3/dir4/dir5/dir6/ HTTP/1.1" 405 253____________________________________________________________________________
The application is dependent on receiving a 405 in this scenario, has anyone else had this situation before?