mirror of
https://github.com/sigoden/dufs.git
synced 2026-04-08 16:49:02 +03:00
[GH-ISSUE #608] Some files failed to upload with reverse proxy #361
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Cusox on GitHub (Aug 7, 2025).
Original GitHub issue: https://github.com/sigoden/dufs/issues/608
Problem
When using reverse proxy, some files upload successfully, but others return a 401 status code.
When using http + port, the files all upload successfully.
Configuration
compose.yaml:
Log
dufs logs:
caddy logs:
Environment Information
@sigoden commented on GitHub (Aug 7, 2025):
Sorry, I cannot confim the bug.
You need to confirm whether the file has been uploaded correctly. The logs don't show any issues.
When using HTTP Digest Authentication, there are usually two HTTP requests:
So it's normal to encounter 401.
@Cusox commented on GitHub (Aug 7, 2025):
@sigoden Thanks for your reply! Actually, only the file
user_de.tar.zstanddata.tar.zstuploaded successfully. As reported in the caddy logs, the other files all havewrite: broken pipeerror, and dufs only returns 401 for those files, but not 200 OK or other success status (e.g. 207 in the logs). The error returned to the client is 502, which may be caused by caddy.@sigoden commented on GitHub (Aug 8, 2025):
The dufs log records all requests. If there's no record, it likely means the request was never sent or hasn't completed yet (such as when an upload is still in progress).
Even if a request is suddenly interrupted, dufs will log the error.
You can use this information to analyze whether there is actually an issue between the reverse proxy and dufs.