Consider cache-control: public for /assets #10600

New Issue

GiteaMirror · 2025-11-02T09:12:20-06:00

GiteaMirror commented

2025-11-02 09:12:20 -06:00

Originally created by @silverwind on GitHub (Apr 6, 2023).

Feature Description

As requested on Discord, I think it makes sense to have the assets that have contenthash in their filename cacheable by intermediary proxies via cache-control: public to take off some load from the gitea process.

For files that do not have contenthash like serviceworker.js and more, I'm not sure. I think we may have to exclude them or (ideally) change them to have a contenthash.

Also I do think we can raise the default cache duration for contenthash assets significantly. They are essentially immutable.

Originally created by @silverwind on GitHub (Apr 6, 2023). ### Feature Description As requested on Discord, I think it makes sense to have the assets that have `contenthash` in their filename cacheable by intermediary proxies via `cache-control: public` to take off some load from the gitea process. For files that do not have `contenthash` like `serviceworker.js` and more, I'm not sure. I think we may have to exclude them or (ideally) change them to have a `contenthash`. Also I do think we can raise the default cache duration for `contenthash` assets significantly. They are essentially immutable.

GiteaMirror added the performance/cpu type/enhancement type/proposal labels 2025-11-02 09:12:20 -06:00

GiteaMirror closed this issue

2025-11-02 09:12:20 -06:00

GiteaMirror commented

2025-11-02 09:12:21 -06:00

@silverwind commented on GitHub (Apr 8, 2023):

If serviceworker.js is the last holdout without contenthash, I would consider removing it. It serves no real purpose for Gitea, except being a unnecessary cache layer, while browser HTTP cache already works.

@silverwind commented on GitHub (Apr 8, 2023): If `serviceworker.js` is the last holdout without contenthash, I would consider removing it. It serves no real purpose for Gitea, except being a unnecessary cache layer, while browser HTTP cache already works.

GiteaMirror commented

2025-11-02 09:12:21 -06:00

@wxiaoguang commented on GitHub (Apr 23, 2025):

We have it now

@wxiaoguang commented on GitHub (Apr 23, 2025): We have it now ![Image](https://github.com/user-attachments/assets/67972d39-6e94-4b51-ae7e-e1e610fb0b47)

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#10600

Consider cache-control: public for /assets #10600

Feature Description

Consider `cache-control: public` for `/assets` #10600