@sigoden commented on GitHub (Jul 29, 2025):
2025-07-29T20:04:50+08:00 INFO - 192.168.8.8 "GET /" 200
2025-07-29T20:04:50+08:00 INFO - 192.168.8.8 "GET…
@sigoden commented on GitHub (Aug 6, 2025):
Sorry, I cannot reproduce the bug.
@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…
@Cusox commented on GitHub (Aug 7, 2025):
Sorry, I cannot confim the bug.对不起，我无法确认该错误。
You need to confirm whether the file has been uploaded…
@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…
@sigoden commented on GitHub (Aug 14, 2025):
We will not support this feature.
Hash calculation requires additional resources, and the larger the file size, the…
@sigoden commented on GitHub (Aug 9, 2025):
I don't think it's a dufs issue. Below is the dufs response header, which shouldn't cause a cache problem.
HTTP/1.…
@yuf19-2022 commented on GitHub (Aug 9, 2025):
I don't think it's a dufs issue. Below is the dufs response header, which shouldn't cause a cache problem.我不认…
@sigoden commented on GitHub (Aug 10, 2025):
I cannot confirm the bug. Even if Edge has this bug, the DUFS layer cannot handle it.
@yuf19-2022 commented on GitHub (Aug 9, 2025):
I don't think it's a dufs issue. Below is the dufs response header, which shouldn't cause a cache problem.我不…