Closed Bug 1164221 Opened 10 years ago Closed 7 years ago

docker-worker: Set Cache-Control headers for S3 artifacts

Categories

(Taskcluster :: Workers, defect)

Product:
Taskcluster
Component:
Workers
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: jonasfj, Unassigned)

References

Details

(Whiteboard: [docker-worker])

Set headers: Cache-Control: public, no-transform (public artifact bucket) Cache-Control: private, no-transform (private artifact bucket) Expires: <date-time of artifact expiration, ie. when we plan to delete it> This pretty much no brainer. Benefits includes that things will be cached correctly by HTTP proxies, which is important. As we make s3-copy-proxy more generic we might want to make it respect cache-control. And in data-center etc. we might very well be dealing with generic HTTP proxies.
Actually, if anyone know someone who can do an additional r+ on the configuration of these headers, that would be good. Ideally we want to get these right the first time.
See Also: → 1155645
See Also: → 1164961
Component: TaskCluster → Docker-Worker
Product: Testing → Taskcluster
Depends on: 1190016
Whiteboard: [docker-worker]
Component: Docker-Worker → Worker
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
Component: Worker → Workers
You need to log in before you can comment on or make changes to this bug.