Michael Krotscheck ebb06fb49f Added CORS support to Cue ... This adds the CORS support middleware to Cue, allowing a deployer to optionally configure rules under which a javascript client may break the single-origin policy and access the API directly. For cue, the middleware was added directly to the application factory, including various default headers usually required by keystone. Note that the CORS middleware must be the first one in the middleware chain, so that it can annotate all responses - even error responses - generated by other middleware. oslo_config initialization was added to the functional test initialization, in order to ensure that a fully initialized config instance is available during tests. 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: I7ff60a96f545ff991de06073a80a5750512ebd31		2015-12-23 11:00:45 -08:00
..
apache2	Run cue-api behind Apache2	2015-03-04 13:08:01 -08:00
cue	Added CORS support to Cue	2015-12-23 11:00:45 -08:00