diff options
| author | Tushar Gohad <tushar.gohad@intel.com> | 2014-11-06 11:40:01 -0700 |
|---|---|---|
| committer | Tushar Gohad <tushar.gohad@intel.com> | 2014-11-06 11:43:41 -0700 |
| commit | 3870f6b055dd91179bdac670ee417ef74b2a4ed3 (patch) | |
| tree | 566c8eb06914450060cd9944f69d3e1566a87358 /doc/modules | |
| parent | 01d5e8738b1ca22641badd35fc28b912c51f93fb (diff) | |
| download | eventlet-3870f6b055dd91179bdac670ee417ef74b2a4ed3.tar.gz | |
wsgi: Add send_hundred_continue_response() API to the docs
Diffstat (limited to 'doc/modules')
| -rw-r--r-- | doc/modules/wsgi.rst | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/doc/modules/wsgi.rst b/doc/modules/wsgi.rst index 6fecdbd..4d4d634 100644 --- a/doc/modules/wsgi.rst +++ b/doc/modules/wsgi.rst @@ -113,3 +113,18 @@ as shown in the following example:: You can find a more elaborate example in the file: ``tests/wsgi_test.py``, :func:`test_024a_expect_100_continue_with_headers`. + +Per HTTP RFC 7231 (http://tools.ietf.org/html/rfc7231#section-6.2) a client is +required to be able to process one or more 100 continue responses. A sample +use case might be a user protocol where the server may want to use a 100-continue +response to indicate to a client that it is working on a request and the +client should not timeout. + +To support multiple 100-continue responses, evenlet wsgi module exports +the API :func:`send_hundred_continue_response`. + +Sample use cases for chunked and non-chunked HTTP scenarios are included +in the wsgi test case ``tests/wsgi_test.py``, +:func:`test_024b_expect_100_continue_with_headers_multiple_chunked` and +:func:`test_024c_expect_100_continue_with_headers_multiple_nonchunked`. + |
