Skip to content

Cache report data in the browser (using ETag & If-None-Match) #535

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 2 commits into from
Aug 17, 2025
Merged

Cache report data in the browser (using ETag & If-None-Match) #535

merged 2 commits into from
Aug 17, 2025

Conversation

Rello
Copy link
Owner

@Rello Rello commented Aug 10, 2025

Summary

  • cache report data in local storage keyed by report id or token
  • send If-Modified-Since header and reuse cached data on 304 responses
  • refetch data when the server returns 304 but no cache exists

Testing

  • node --check js/report.js
  • npm test (fails: Missing script "test")

https://chatgpt.com/codex/tasks/task_e_68982862132c8333b1d27c24f6532bd4

@Rello Rello changed the title Add frontend caching using If-Modified-Since Cache report data in the browser (using ETag & If-None-Match) Aug 17, 2025
@Rello Rello merged commit 764b126 into master Aug 17, 2025
1 check passed
@Rello Rello deleted the codex/find-best-approach-to-cache-report-data branch August 17, 2025 14:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
codex
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@Rello