[GH-ISSUE #450] Why use [ dufs -a "@/:rw" ] in webdav fail? it's shows unauth when i try use no username and passwd #242

New Issue

zhus · 2026-04-08T16:51:26+03:00

zhus commented

2026-04-08 16:51:26 +03:00

Originally created by @zhi2xin1 on GitHub (Sep 6, 2024).
Original GitHub issue: https://github.com/sigoden/dufs/issues/450

Problem

Why use [ dufs -a "@/:rw" ] in webdav fail? it's shows unauth when i try use no username and passwd

The client is AIMP play run in my android phone.
When I use admin:admin to login it works(this time with -a admin:admin)

Configuration

use with no config file

Log

.\dufs.exe -a "@/:rw"
Listening on:
http://127.0.0.1:5000/
http://192.168.2.16:5000/
http://[::1]:5000/

2024-09-06T23:51:47+08:00 INFO - 192.168.2.9 "PROPFIND /" 401
2024-09-06T23:51:48+08:00 INFO - 192.168.2.9 "PROPFIND /" 401

Screenshots/Media

Environment Information

Dufs version: 0.42.0
Browser/Webdav info: webdav
OS info: windows
Proxy server (if any): no proxy

Originally created by @zhi2xin1 on GitHub (Sep 6, 2024). Original GitHub issue: https://github.com/sigoden/dufs/issues/450 **Problem** Why use [ dufs -a "@/:rw" ] in webdav fail? it's shows unauth when i try use no username and passwd The client is AIMP play run in my android phone. When I use admin:admin to login it works(this time with -a admin:admin)  **Configuration** use with no config file   **Log** .\dufs.exe -a "@/:rw" Listening on: http://127.0.0.1:5000/ http://192.168.2.16:5000/ http://[::1]:5000/ 2024-09-06T23:51:47+08:00 INFO - 192.168.2.9 "PROPFIND /" 401 2024-09-06T23:51:48+08:00 INFO - 192.168.2.9 "PROPFIND /" 401  **Screenshots/Media**  **Environment Information** - Dufs version: 0.42.0 - Browser/Webdav info: webdav - OS info: windows - Proxy server (if any):  no proxy

zhus closed this issue

2026-04-08 16:51:26 +03:00

zhus commented

2026-04-08 16:51:27 +03:00

@sigoden commented on GitHub (Sep 6, 2024):

dufs -a @/:rw is misconfig, use dufs -A instead.

And I cannot confirm the 401 problem.

@sigoden commented on GitHub (Sep 6, 2024): `dufs -a @/:rw` is misconfig, use `dufs -A` instead. And I cannot confirm the 401 problem.

zhus commented

2026-04-08 16:51:27 +03:00

@zhi2xin1 commented on GitHub (Sep 7, 2024):

dufs -a @/:rw is misconfig, use dufs -A instead.

And I cannot confirm the 401 problem.

Maybe you missunderstand my mean, I try to use -a to set user not use -A to set file auth, and the problem is that I can't login without username and passwd

@zhi2xin1 commented on GitHub (Sep 7, 2024): > `dufs -a @/:rw` is misconfig, use `dufs -A` instead. > > And I cannot confirm the 401 problem. Maybe you missunderstand my mean, I try to use -a to set user not use -A to set file auth, and the problem is that I can't login without username and passwd

zhus commented

2026-04-08 16:51:27 +03:00

@sigoden commented on GitHub (Sep 7, 2024):

@zhi2xin1

You have two problems:

Misconfiguration

If you want everyone to be able to access every file with read and write permissions, you should run dufs -A. If you want everyone to have read-only access to all files, you should run dufs.

Dufs uses --allow-* to permit operations. If you do not allow write operations such as --allow-upload or --allow-delete, setting the auth to @/:rw is meaningless.

Cannot reproduce

Even when we run dufs -a @/:rw, everything is fine; We can perform the desired actions without needing to log in； we cannot reproduce the 401 error that your logs indicate.

Final

Please provide more detailed information for reproducing, including configuration, execution commands, and screenshots (on webdav client). Otherwise, we won't be able to assist you.

@sigoden commented on GitHub (Sep 7, 2024): @zhi2xin1 You have two problems: ### Misconfiguration If you want everyone to be able to access every file with read and write permissions, you should run `dufs -A`. If you want everyone to have read-only access to all files, you should run `dufs`. Dufs uses `--allow-*` to permit operations. If you do not allow write operations such as `--allow-upload` or `--allow-delete`, setting the auth to `@/:rw` is meaningless. ### Cannot reproduce Even when we run `dufs -a @/:rw`, everything is fine; We can perform the desired actions without needing to log in； we cannot reproduce the 401 error that your logs indicate. ## Final Please provide more detailed information for reproducing, including configuration, execution commands, and screenshots (on webdav client). Otherwise, we won't be able to assist you.

zhus referenced this issue

2026-04-08 16:53:19 +03:00

[PR #242] [MERGED] chore: update ci #531

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: sigoden/dufs#242