f828a9969e
This adds the CORS support middleware to Manila, allowing a deployer to optionally configure rules under which a javascript client may break the single-origin policy and access the API directly. For Manila, the paste.ini method of deploying the middleware was chosen, because it needs to be able to annotate error responses created by other middlewares. If one such middleware throws an error - such as an auth error from keystone - that error response must still have CORS headers in order to be readable by the user agent. OpenStack CrossProject Spec: http://specs.openstack.org/openstack/openstack-specs/specs/cors-support.html Oslo_Middleware Docs: http://docs.openstack.org/developer/oslo.middleware/cors.html OpenStack Cloud Admin Guide: http://docs.openstack.org/admin-guide-cloud/cross_project_cors.html Change-Id: I9d4b6d0eb380da3eae3867fcebe30fdd5824978d
9 lines
227 B
Plaintext
9 lines
227 B
Plaintext
[DEFAULT]
|
|
output_file = etc/manila/manila.conf.sample
|
|
namespace = manila
|
|
namespace = oslo.messaging
|
|
namespace = oslo.middleware.cors
|
|
namespace = oslo.db
|
|
namespace = oslo.db.concurrency
|
|
namespace = keystonemiddleware.auth_token
|