summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorMichael Krotscheck <krotscheck@gmail.com>2015-11-02 12:05:17 -0800
committerMichael Krotscheck <krotscheck@gmail.com>2015-11-16 17:26:51 -0800
commit4e7bb27895f6876ada3a8b19272422af29e75d22 (patch)
tree31240dcaed7163a7d23c79628187788c1ca5e2ad /doc
parent6121b6782c7c588515030ebf418c1e5b262d237b (diff)
downloadoslo-middleware-4e7bb27895f6876ada3a8b19272422af29e75d22.tar.gz
Enable latent CORS configuration via pastedeploy
In the case where paste deployment and oslo are used in concert, it is not possible for an application to easily ship required configuraton properties, such as custom headers, with their release artifact. This patch adds parameters which expose set_latent to paste.ini users, permitting the above. Tests and documentation have been updated. Change-Id: Id98002f6813055efe698f0b96a3e0d408c58ed7c
Diffstat (limited to 'doc')
-rw-r--r--doc/source/cors.rst6
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/source/cors.rst b/doc/source/cors.rst
index 11cb043..368b248 100644
--- a/doc/source/cors.rst
+++ b/doc/source/cors.rst
@@ -115,6 +115,12 @@ configuration, this may be done as follows.::
# Optional field, in case the program name is different from the project:
oslo_config_program = oslo_project_name-api
+ # This method also permits setting latent properties, for any origins set
+ # in oslo config.
+ latent_allow_headers=X-Auth-Token
+ latent_expose_headers=X-Auth-Token
+ latent_methods=GET,PUT,POST
+
Configuration Options
---------------------