On Mon, 5 Feb 2018, Fred De Backer wrote:
Therefore it is my opinion that the Openstack API (Nova in this case, but
equally valid for all other APIs) should be responsible to include proper
HTTP headers in their responses to either disallow caching of the response
or at least limit it's validity.
Yeah, that is what should happen. We recently did it (disallow
caching) for placement
(http://specs.openstack.org/openstack/nova-specs/specs/queens/approved/placement-cache-headers.html)
but it probably needs to be done just about everywhere else.
I'd suggest you create a bug (probably just a nova one for now, but
make it general enough that it is easy to add other projects) an
perhaps that will help get some traction.
--
Chris Dent (⊙＿⊙') https://anticdent.org/
freenode: cdent tw: @anticdent
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
