@sigoden commented on GitHub (Feb 8, 2025):
No way. Please don't use -A then set the --allow-* options one by one.
@fredleger commented on GitHub (Feb 11, 2025):
for the record i also tried setting auth: [] in dufs.yaml and it's "worked". I have access in RW mode to all…
@sigoden commented on GitHub (Feb 12, 2025):
Maybe you missed the options --allow-all or --allow-upload/--allow-delete.
:
see https://github.com/sigoden/dufs/issues/395#issuecomment-2156184447
@sigoden commented on GitHub (Feb 1, 2025):
similar to #263
Webdav must be designed like this.
This is because some webdav clients do not carry the Authorizati…
@sigoden commented on GitHub (Jan 27, 2025):
https://github.com/sigoden/dufs/issues/519#issuecomment-2567204564 provides a detailed explanation.
@ogarcia commented on GitHub (Feb 2, 2025):
You have to forgive me but it's to get it right. You say that the webdav client does not send the authorization…
@sigoden commented on GitHub (Feb 2, 2025):
For some webdav clients, even if you enter username/password, it will not automatically carry authorization…
@ogarcia commented on GitHub (Feb 2, 2025):
Ah. Ok. It's a workaround for certain webdav clients that should make the authenticated request and don't do it.…