Opened 8 years ago

Closed 8 years ago

#5246 closed enhancement (implemented)

Look into caching using HTTP headers

Reported by: karsten Owned by: karsten
Priority: Medium Milestone:
Component: Metrics/Onionoo Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

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.)

Child Tickets

Change History (1)

comment:1 Changed 8 years ago by karsten

Resolution: implemented
Status: newclosed

Implemented using Last-Modified/If-Modified-Since headers. We can always make it fancier later. Closing.

Note: See TracTickets for help on using tickets.