
On Thu, Jan 14, 2021 at 10:55:46AM +0800, Li Ping wrote:
On Thu, Jan 14, 2021 at 09:08:50AM +0800, Wu Fengguang wrote:
On Wed, Jan 13, 2021 at 09:19:47PM +0800, Li Ping wrote:
[why] find a -type d a a/b a/c find a -type d -exec curl -sSf -X MKCOL "$http_url/{}" \; ==> curl: (22) The requested URL returned error: 409 Conflict reason: upload an empty folder causes this error.
I suspect 409 happens because server side already have that dir. It's like you run
That's what I thought at first, then I make new dir, upload the new dir also causes this error.
if I create new file under the dir would not cause this error. so i think there is no need to upload empty folder at all.
No "think" please. You should give clear statement, like "webdav supports auto-and-recursively create dirs when uploading some dir_level1/dir_level2/file". And prove it with commandline examples or webdav API definitions. Whether or not your patch is right, the changelog is not clear enough to prove whether it's "definitely/always right" or "right by chance".
mkdir a => success mkdir a => 409
But will the server side auto create new subdirs if they do not already exist? Probably the below find will fail.
Please experiment with deeper dirs, like a/b/c/file
Actually, I have experimented with deeper dirs
Then please showcase it in changelog. BTW, please try this example https://stackoverflow.com/questions/42941176/how-to-create-directories-recur... If our webdav server can auto create subdirs, then what's the difference in our server comparing to the standard/old one? Thanks, Fengguang