Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #5246

Closed (moved)
(moved)
Open
Created Feb 27, 2012 by Karsten Loesing@karsten

Look into caching using HTTP headers

The current caching strategy is non-existent. We should find out which HTTP headers are most commonly used to tell clients and proxies how to cache our JSON responses. The caching strategy may rely on information that the server has about new data becoming available.

Arturo says there are two caching approaches: first, the server says how long a document will be valid; second, a client may check whether its copy of a document is still the most recent document there is. We should probably implement both approaches.

(This was issue 6 in my GitHub repository.)

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking