yahoo-eng-team team mailing list archive

[Chris Dent <cdent+lp@xxxxxxxxxxxxx>]

Public bug reported:

In version 1.0 of the placement API, responses are sent without any
cache-busting headers. This means that the responses may be cached by
the user-agent. It's not predictable.

Caching of resource providers is not desired so it would be good to send
cache headers to enforce that responses are not cached.

This old document remains the bizness for learning how to do such
things: https://www.mnot.net/cache_docs/

** Affects: nova
     Importance: Medium
         Status: Triaged


** Tags: placement

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1632852

Title:
  placement api responses should not be cacehable

Status in OpenStack Compute (nova):
  Triaged

Bug description:
  In version 1.0 of the placement API, responses are sent without any
  cache-busting headers. This means that the responses may be cached by
  the user-agent. It's not predictable.

  Caching of resource providers is not desired so it would be good to
  send cache headers to enforce that responses are not cached.

  This old document remains the bizness for learning how to do such
  things: https://www.mnot.net/cache_docs/

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1632852/+subscriptions