Prevent shared caches from storing live Gitea API responses #109

Closed
opened 2026-08-06 13:46:16 +00:00 by rockachopa · 0 comments
Member

Evidence: /api/v1/context and /api/v1/events return live authenticated Gitea-derived data without a Cache-Control policy. An intermediary cache can retain and replay stale user, issue, pull-request, or activity data. Add Cache-Control: no-store to both live API responses, including degraded/retryable responses, with behavioral coverage.

Evidence: `/api/v1/context` and `/api/v1/events` return live authenticated Gitea-derived data without a `Cache-Control` policy. An intermediary cache can retain and replay stale user, issue, pull-request, or activity data. Add `Cache-Control: no-store` to both live API responses, including degraded/retryable responses, with behavioral coverage.
timmy was assigned by rockachopa 2026-08-06 13:46:16 +00:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: stackchain/stackchain-dashboard#109
No description provided.