Closed Bug 1336000 Opened 8 years ago Closed 8 years ago

Aggregates service should send caching headers

Categories

(Cloud Services Graveyard :: Metrics: Pipeline, defect, P1)

Product:
Cloud Services Graveyard
Component:
Metrics: Pipeline
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: rbarnes, Assigned: frank)

References

Details

The aggregates served by aggregates.telemetry.m.o are immutable. If you send the same URL, you always get the same results (or at least it seems like you should). You should indicate this with "Cache-Control: immutable" to allow the browser to cache these results more efficiently.
Blocks: 1255755
Component: Telemetry Server → Metrics: Pipeline
Priority: -- → P3
Product: Webtools → Cloud Services
Summary: Telemetry data should send caching headers → Aggregates service should send caching headers
Version: Trunk → unspecified
Points: --- → 1
This isn't true for all aggregates, only for submission-date aggregates. Build-id aggregates transform over time.
Priority: P3 → P2
We'll add cache control headers for all aggregates types. For now, build-id aggregates will expire after 12 hours.
Priority: P2 → P1
Assignee: nobody → fbertsch
Dang are reloads are faster now.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Product: Cloud Services → Cloud Services Graveyard
You need to log in before you can comment on or make changes to this bug.