sigoden/dufs
1
0
Fork 0
mirror of https://github.com/sigoden/dufs.git synced 2026-04-08 16:49:02 +03:00
Code Issues 8 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #610] static file update not take effect #364

New Issue
Closed
opened 2026-04-08 16:52:22 +03:00 by zhus · 5 comments
zhus commented 2026-04-08 16:52:22 +03:00
Owner
Copy Link

Originally created by @yuf19-2022 on GitHub (Aug 9, 2025).
Original GitHub issue: https://github.com/sigoden/dufs/issues/610

Problem

deploy a static html website,when i update some file, some computer show the old page,i need to clear browser cache,but i cannot make everyone do this.

Configuration

Log

Screenshots/Media

Environment Information

  • Dufs version:o.43.0
  • Browser/Webdav info:chrome and so on
  • OS info:windows 10 or more
  • Proxy server (if any): nginx
Originally created by @yuf19-2022 on GitHub (Aug 9, 2025). Original GitHub issue: https://github.com/sigoden/dufs/issues/610 **Problem** deploy a static html website,when i update some file, some computer show the old page,i need to clear browser cache,but i cannot make everyone do this. **Configuration** <!-- Please specify the Dufs command-line arguments or configuration used. --> <!-- If the issue is related to authentication/permissions, include auth configurations while concealing sensitive information (e.g., passwords). --> **Log** <!-- Attach relevant log outputs that can help diagnose the issue. --> **Screenshots/Media** <!-- If applicable, add screenshots or videos that help illustrate the issue, especially for WebUI problems. --> **Environment Information** - Dufs version:o.43.0 - Browser/Webdav info:chrome and so on - OS info:windows 10 or more - Proxy server (if any): <!-- e.g. nginx, cloudflare -->nginx
zhus closed this issue 2026-04-08 16:52:22 +03:00
zhus commented 2026-04-08 16:52:22 +03:00
Author
Owner
Copy Link

@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.1 200 OK
cache-control: no-cache
last-modified: Sat, 02 Aug 2025 01:19:35 GMT
etag: "1754097575165-2221"
content-type: text/html; charset=UTF-8
content-disposition: inline; filename="test.html"
accept-ranges: bytes
content-length: 2221
date: Sat, 09 Aug 2025 01:18:05 GMT
<!-- gh-comment-id:3169613705 --> @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.1 200 OK cache-control: no-cache last-modified: Sat, 02 Aug 2025 01:19:35 GMT etag: "1754097575165-2221" content-type: text/html; charset=UTF-8 content-disposition: inline; filename="test.html" accept-ranges: bytes content-length: 2221 date: Sat, 09 Aug 2025 01:18:05 GMT ```
zhus commented 2026-04-08 16:52:23 +03:00
Author
Owner
Copy Link

@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.我不认为这是一个 dufs 问题。下面是 dufs 响应标头，它不会导致缓存问题。

HTTP/1.1 200 OK
cache-control: no-cache
last-modified: Sat, 02 Aug 2025 01:19:35 GMT
etag: "1754097575165-2221"
content-type: text/html; charset=UTF-8
content-disposition: inline; filename="test.html"
accept-ranges: bytes
content-length: 2221
date: Sat, 09 Aug 2025 01:18:05 GMT

I have to open console,and check the disable cache,otherwise the request is from memory cache

<!-- gh-comment-id:3169619554 --> @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.我不认为这是一个 dufs 问题。下面是 dufs 响应标头，它不会导致缓存问题。 > > ``` > HTTP/1.1 200 OK > cache-control: no-cache > last-modified: Sat, 02 Aug 2025 01:19:35 GMT > etag: "1754097575165-2221" > content-type: text/html; charset=UTF-8 > content-disposition: inline; filename="test.html" > accept-ranges: bytes > content-length: 2221 > date: Sat, 09 Aug 2025 01:18:05 GMT > ``` I have to open console,and check the disable cache,otherwise the request is from memory cache
zhus commented 2026-04-08 16:52:23 +03:00
Author
Owner
Copy Link

@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.我不认为这是一个 dufs 问题。下面是 dufs 响应标头，它不会导致缓存问题。我不认为这是一个 dufs 问题。下面是 dufs 响应标头，它不会导致缓存问题。我不认为这是一个 dufs 问题。下面是 dufs 响应标头，它不会导致缓存问题。

HTTP/1.1 200 OK
cache-control: no-cache
last-modified: Sat, 02 Aug 2025 01:19:35 GMT
etag: "1754097575165-2221"
content-type: text/html; charset=UTF-8
content-disposition: inline; filename="test.html"
accept-ranges: bytes
content-length: 2221
date: Sat, 09 Aug 2025 01:18:05 GMT

I have to open console,and check the disable cache,otherwise the request is from memory cache我必须打开控制台，并检查禁用缓存，否则请求来自内存缓存

even this,sometime it not take effect yet

<!-- gh-comment-id:3169620542 --> @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.我不认为这是一个 dufs 问题。下面是 dufs 响应标头，它不会导致缓存问题。我不认为这是一个 dufs 问题。下面是 dufs 响应标头，它不会导致缓存问题。我不认为这是一个 dufs 问题。下面是 dufs 响应标头，它不会导致缓存问题。 > > ``` > > HTTP/1.1 200 OK > > cache-control: no-cache > > last-modified: Sat, 02 Aug 2025 01:19:35 GMT > > etag: "1754097575165-2221" > > content-type: text/html; charset=UTF-8 > > content-disposition: inline; filename="test.html" > > accept-ranges: bytes > > content-length: 2221 > > date: Sat, 09 Aug 2025 01:18:05 GMT > > ``` > > I have to open console,and check the disable cache,otherwise the request is from memory cache我必须打开控制台，并检查禁用缓存，否则请求来自内存缓存 even this,sometime it not take effect yet
zhus commented 2026-04-08 16:52:23 +03:00
Author
Owner
Copy Link

@sigoden commented on GitHub (Aug 9, 2025):

Then you can run curl -I <url> to compare the headers before and after the modification to see what has changed.

<!-- gh-comment-id:3169625327 --> @sigoden commented on GitHub (Aug 9, 2025): Then you can run `curl -I <url>` to compare the headers before and after the modification to see what has changed.
zhus commented 2026-04-08 16:52:23 +03:00
Author
Owner
Copy Link

@yuf19-2022 commented on GitHub (Aug 16, 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.1 200 OK
cache-control: no-cache
last-modified: Sat, 02 Aug 2025 01:19:35 GMT
etag: "1754097575165-2221"
content-type: text/html; charset=UTF-8
content-disposition: inline; filename="test.html"
accept-ranges: bytes
content-length: 2221
date: Sat, 09 Aug 2025 01:18:05 GMT

but my response is
IMG_20250816_165036.jpg

<!-- gh-comment-id:3193507187 --> @yuf19-2022 commented on GitHub (Aug 16, 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.1 200 OK > cache-control: no-cache > last-modified: Sat, 02 Aug 2025 01:19:35 GMT > etag: "1754097575165-2221" > content-type: text/html; charset=UTF-8 > content-disposition: inline; filename="test.html" > accept-ranges: bytes > content-length: 2221 > date: Sat, 09 Aug 2025 01:18:05 GMT > ``` but my response is ![IMG_20250816_165036.jpg](https://github.com/user-attachments/assets/7d3abba6-a8b2-494a-acaf-271ed1525548)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
help wanted
pull-request
Mirrored from GitHub Pull Request
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
zhus
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sigoden/dufs#364
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?