fix(api): disable caching for cloud API responses (#14)
CD — Deployment / deploy (push) Successful in 17s

Browsers applied heuristic caching to JSON API responses because no
Cache-Control header was set, serving stale file lists after delete or
upload even with a hard refresh. Force no-store on all /api/cloud/*
responses.

---------

Co-authored-by: xEsiah <[email protected]>
Reviewed-on: #14
Reviewed-by: Esiah <[email protected]>
Co-authored-by: Gitea Actions <-[email protected]>
This commit was merged in pull request #14.
This commit is contained in:
Gitea Actions
2026-10-20 12:09:07 +00:00
committed by Esiah
co-authored by Esiah
parent bdf2daa5f3
commit cbe33bf563
+8
View File
@@ -79,6 +79,14 @@ const SELECT_USER = `
LEFT JOIN user_avatars ua ON ua.user_id = u.id`;
export const registerAuthRoutes = (app: App, db: Db, config: Config): void => {
// Aucune reponse de l'API ne doit etre mise en cache. Sans en-tete explicite,
// les navigateurs appliquent un cache heuristique et reservent une liste de
// fichiers obsolete apres une suppression ou un depot.
app.use("/api/cloud/*", async (context, next) => {
await next();
context.header("cache-control", "no-store");
});
app.use("/api/cloud/*", attachUser(db));
const limiter = createRateLimiter(config.RATE_LIMIT_LOGIN_MAX, config.RATE_LIMIT_LOGIN_WINDOW_MS);