Add minimum cache headers to placement service
RFC 7232[1] says that a web service should send a last-modified header for any representation for a last-modified time can reasonable be deduced. The placement service does not currently do this. Including it will make it a better HTTP citizen and also provide useful metadata in the response. If a last-modified header is added then it is also necessary to add a cache-control header with a value of "no-cache" to insure that clients and proxies are not inclined to cache representations provided by the placement service.
Since adding a new header requires a new microversion a full-blown spec will be created and linked here when ready.
Blueprint information
- Status:
- Complete
- Approver:
- Sylvain Bauza
- Priority:
- Low
- Drafter:
- Chris Dent
- Direction:
- Approved
- Assignee:
- Chris Dent
- Definition:
- Approved
- Series goal:
- Accepted for queens
- Implementation:
-
Implemented
- Milestone target:
-
queens-3
- Started by
- Matt Riedemann
- Completed by
- Matt Riedemann
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Add a spec for minimal cache headers in placement
Gerrit topic: https:/
Addressed by: https:/
WIP: [placement] manage cache headers
Addressed by: https:/
[placement] manage cache headers for inventories
Addressed by: https:/
[placement] manage cache headers for resource classes
Addressed by: https:/
[placement] manage cache headers for usages
Addressed by: https:/
[placement] manage cache headers for aggregates
Addressed by: https:/
[placement] manage cache headers for allocations
Addressed by: https:/
[placement] Object changes to support last-modified headers
Addressed by: https:/
[placement] Add cache headers to placement api requests
