Closed lyh458 closed 2 years ago
It seems that the requests logged with an error don't have the Authorization header set, which would be necessary to pass basicauth. Maybe a problem in the client?
(I only glanced at this quickly, apologies if I am missing something obvious. I also don't actually know too much about webdav, I just wrapped an underlying library.)
It seems that the requests logged with an error don't have the Authorization header set, which would be necessary to pass basicauth. Maybe a problem in the client?
(I only glanced at this quickly, apologies if I am missing something obvious. I also don't actually know too much about webdav, I just wrapped an underlying library.)
@mholt thanks the reply. Maybe you are right, I have tried to use other webdav clients to upload files to my server after seeing your reply, some worked, some did't.
I will close the issue and report the issue to the client's author.
Hi,
Thanks for the awesome work. There is an issue trouble me when I use this module. Large file can not be upload to the webdav server even
caddy
andcaddy-webdav
start normally. However, small file can be uploaded and deleted, and large file can alse be deleted. And all is well ifbasicauth
is not set, similar to the issue mentioned here. Here is my detailed info:version
my
Caddyfile
dav.mydomain.com { log { output file /var/log/caddy/caddy.log } header { Access-Control-Allow-Origin * Access-Control-Allow-Credentials true Access-Control-Allow-Methods "GET, HEAD, POST, PUT, OPTIONS, MOVE, DELETE, COPY, LOCK, UNLOCK, PROPFIND, MKCOL" Access-Control-Allow-Headers "Authorization,DNT,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,X-Accept-Charset,X-Accept,origin,accept,if-match,destination,overwrite,X-CustomHeader" Access-Control-Expose-Headers "ETag" Access-Control-Max-Age 1728000 } file_server webdav { root /data/webdav } basicauth { username JDJhJDE0JGxYYWhxUVd6a1RRd01PS2xtNnBkNHUzUllqenFaSGFib1Zid1BFaGNRSmpOLktXNXBJbGhH } }
Thanks in advance.