11d6ccbb67
There is a bug in request-id middleware that a subsequent API request will overwrite a request-id of a previous request when multiple API calls are processed in parallel in request_id middleware. This commit imports the fix in oslo. cherry-picked from oslo-incubator d7bd9dc37ac3d6bc171cd2e290c772633ad20a32 Closes-Bug: #1289696 ---- Don't store the request ID value in middleware as class variable The original version of the request_id middleware generates a request ID during process_request() and stores the value in a variable, so it can be attached as header in process_request(). This is pretty dangerous, since subsequent requests will overwrite this value, and the wrong request ID may be attached to some responses. This is particularly apparent when requests arrive in parallel. This change replaces process_request() and process_response() with an override of __call__(). This allows the generated req_id to be used in the response header without needing to save it as a class-level variable. ---- Change-Id: Ic20047f604394f1ce4900c3b6a00595223804cba
# -- Welcome!
You have come across a cloud computing network fabric controller. It has identified itself as "Neutron." It aims to tame your (cloud) networking!
# -- External Resources:
The homepage for Neutron is: http://launchpad.net/neutron . Use this site for asking for help, and filing bugs. Code is available on github at <http://github.com/openstack/neutron>.
The latest and most in-depth documentation on how to use Neutron is available at: <http://docs.openstack.org>. This includes:
Neutron Administrator Guide http://docs.openstack.org/trunk/openstack-network/admin/content/
Neutron API Reference: http://docs.openstack.org/api/openstack-network/2.0/content/
The start of some developer documentation is available at: http://wiki.openstack.org/NeutronDevelopment
For help using or hacking on Neutron, you can send mail to <mailto:openstack-dev@lists.openstack.org>.