yahoo-eng-team team mailing list archive

[OpenStack Infra <1524671@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

https://review.openstack.org/236988
\Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
Your project "openstack/neutron" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to.

commit 7f65b06033afca20399305f285ff5e6d43c5131c
Author: Michael Krotscheck <krotscheck@xxxxxxxxx>
Date:   Mon Oct 19 06:52:04 2015 -0700

    Added CORS support to Neutron
    
    This adds the CORS support middleware to Neutron, allowing a deployer
    to optionally configure rules under which a javascript client may
    break the single-origin policy and access the API directly.
    
    For neutron, both the paste.ini and the direct-wrap method of
    deploying the middleware were chosen, since neutron is in a state of
    migration to pecan. Note that if someone deploys pecan-neutron behind
    other middleware, any responses provided by that middleware will not
    be CORS-enabled, as these responses would be returned before the
    headers could be annotated. This results in a response not 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
    DocImpact: Add link to CORS configuration in admin cloud guide.
    
    Change-Id: I02acea6124d28370d92e7c94ca2d1d6c5c8937ac

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: neutron

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1524671

Title:
      Added CORS support to Neutron

Status in neutron:
  New

Bug description:
  https://review.openstack.org/236988
  \Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
  Your project "openstack/neutron" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to.

  commit 7f65b06033afca20399305f285ff5e6d43c5131c
  Author: Michael Krotscheck <krotscheck@xxxxxxxxx>
  Date:   Mon Oct 19 06:52:04 2015 -0700

      Added CORS support to Neutron
      
      This adds the CORS support middleware to Neutron, allowing a deployer
      to optionally configure rules under which a javascript client may
      break the single-origin policy and access the API directly.
      
      For neutron, both the paste.ini and the direct-wrap method of
      deploying the middleware were chosen, since neutron is in a state of
      migration to pecan. Note that if someone deploys pecan-neutron behind
      other middleware, any responses provided by that middleware will not
      be CORS-enabled, as these responses would be returned before the
      headers could be annotated. This results in a response not 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
      DocImpact: Add link to CORS configuration in admin cloud guide.
      
      Change-Id: I02acea6124d28370d92e7c94ca2d1d6c5c8937ac

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1524671/+subscriptions