Added Keystone and RequestID headers to CORS middleware
CORS middleware's latent configuration feature, new in 3.0.0, allows adding headers that apply to all valid origins. This patch adds headers commonly used in openstack to designate's paste pipeline, so that operators do not have to be aware of additional configuration magic to ensure that browsers can talk to the API. For more information: http://docs.openstack.org/developer/oslo.middleware/cors.html#configuration-for-pastedeploy Change-Id: I47a4f8db1521cdcbf6fbe714aa9b5dbf6df8b5eb
This commit is contained in:
parent
691a5f4c7b
commit
d5303aa898
|
@ -41,6 +41,9 @@ paste.app_factory = designate.api.admin:factory
|
|||
[filter:cors]
|
||||
paste.filter_factory = oslo_middleware.cors:filter_factory
|
||||
oslo_config_project = designate
|
||||
latent_allow_headers = X-Auth-Token, X-Auth-Sudo-Tenant-ID, X-Auth-Sudo-Project-ID, X-Auth-All-Projects, X-Designate-Edit-Managed-Records
|
||||
latent_expose_headers = X-OpenStack-Request-ID, Host
|
||||
latent_allow_methods = GET, PUT, POST, DELETE, PATCH
|
||||
|
||||
[filter:request_id]
|
||||
paste.filter_factory = oslo_middleware:RequestId.factory
|
||||
|
|
Loading…
Reference in New Issue