PUTs and POSTs hang when using wsgiref

Bug #1189648 reported by Kurt Griffiths
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
zaqar
Fix Released
Critical
Kurt Griffiths

Bug Description

wsgiref's wsgi.input stream blocks on read() with no arguments. WSGI transport driver needs to be updated to pass content length to read().

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to marconi (master)

Fix proposed to branch: master
Review: https://review.openstack.org/32579

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to marconi (master)

Reviewed: https://review.openstack.org/32579
Committed: http://github.com/stackforge/marconi/commit/c91c724a052bd405668bdfda9b66f6a8429a06f5
Submitter: Jenkins
Branch: master

commit c91c724a052bd405668bdfda9b66f6a8429a06f5
Author: kgriffs <email address hidden>
Date: Mon Jun 10 18:30:52 2013 -0400

    Pass content length to req.stream.read() in WSGI transport

    This update modifies the WSGI transport driver so that it
    always passes in a length when reading from the request
    stream. This is necessary because WSGI servers are not
    required to provide a stream that supports "read all"
    semantics. For example, wsgiref will simply block if
    read() is called without arguments.

    Fixes: bug #1189648
    Change-Id: I267e3bce36f0e11d931d9e9800bf3ad3aca7a804

Changed in marconi:
status: In Progress → Fix Committed
Changed in marconi:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.