openstack
/
oslo.middleware
Code Issues Proposed changes

Removed simple headers from documentation examples 

These headers were removed from the defaults in
https://review.openstack.org/#/c/293566/ - as they are already
automatically managed in accordance to the CORS specification. This
patch removes them from the example code.

Change-Id: Ic2728d65c31dcd2f6a887ce8b112f544fd5730f3
This commit is contained in:
Michael Krotscheck 2016-05-04 10:25:57 -07:00
parent 9673e63496
commit ea167241d4
No known key found for this signature in database
GPG Key ID: 20E618D878DE38AB
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/source/cors.rst
View File

@ -52,8 +52,8 @@ something like this::
allowed_origin=https://website.example.com:443,https://website2.example.com:443
max_age=3600
allow_methods=GET,POST,PUT,DELETE
allow_headers=Content-Type,Cache-Control,Content-Language,Expires,Last-Modified,Pragma,X-Custom-Header
expose_headers=Content-Type,Cache-Control,Content-Language,Expires,Last-Modified,Pragma,X-Custom-Header
allow_headers=X-Custom-Header
expose_headers=X-Custom-Header
This middleware permits you to override the rules for multiple
`allowed_origin`'s. To express this in your configuration file, first begin
@ -102,8 +102,8 @@ will add CORS support.::
allowed_origin=https://website.example.com:443,https://website2.example.com:443
max_age=3600
allow_methods=GET,POST,PUT,DELETE
allow_headers=Content-Type,Cache-Control,Content-Language,Expires,Last-Modified,Pragma,X-Custom-Header
expose_headers=Content-Type,Cache-Control,Content-Language,Expires,Last-Modified,Pragma,X-Custom-Header
allow_headers=X-Custom-Header
expose_headers=X-Custom-Header
If your application is using pastedeploy, but would also like to use the
existing configuration from oslo_config in order to simplify the points of