tornado.websocket — Bidirectional communication to the browser ## • HTTP servers and clients ☐ tornado.httpserver — Non-blocking HTTP server ☐ tornado.httpclient — Asynchronous HTTP client tornado.httputil is given it will be called with the future when it is ready. ## HTTP servers and clients • tornado.httpserver — Non-blocking HTTP server • HTTP Server • tornado.httpclient — Asynchronous HTTP client HTTP headers and URLs • tornado.http1connection – HTTP/1.x client/server implementation # tornado.httpserver — Non-blocking HTTP server A non-blocking, single-threaded HTTP server. Typical applications

selected by the server. New in version 5.1. ### 6.3 HTTP servers and clients ##### 6.3.1 tornado.httpserver — Non-blocking HTTP server A non-blocking, single-threaded HTTP server. Typical applications httpclient • The io_loop argument to all AsyncHTTPClient constructors has been removed. ### tornado.httpserver • It is now possible for a client to reuse a connection after sending a chunked request. 3 ## Jan 6, 2018 ### tornado.curl\_httpclient • Improved debug logging on Python 3. ### tornado.httpserver • Content-Length and Transfer-Encoding headers are no longer sent with 1xx or 204 responses

selected by the server. New in version 5.1. ### 6.3 HTTP servers and clients ##### 6.3.1 tornado.httpserver — Non-blocking HTTP server ## A non-blocking, single-threaded HTTP server Typical applications httpclient • The io_loop argument to all AsyncHTTPClient constructors has been removed. ### tornado.httpserver • It is now possible for a client to reuse a connection after sending a chunked request. Tornado 4.5.3 Jan 6, 2018 tornado.curl\_httpclient • Improved debug logging on Python 3. ### tornado.httpserver • Content-Length and Transfer-Encoding headers are no longer sent with 1xx or 204 responses

selected by the server. New in version 5.1. ### 5.3 HTTP servers and clients ##### 5.3.1 tornado.httpserver — Non-blocking HTTP server A non-blocking, single-threaded HTTP server. Typical applications httpclient • The io_loop argument to all AsyncHTTPClient constructors has been removed. ### tornado.httpserver • It is now possible for a client to reuse a connection after sending a chunked request. Tornado 4.5.3 Jan 6, 2018 tornado.curl\_httpclient • Improved debug logging on Python 3. ### tornado.httpserver • Content-Length and Transfer-Encoding headers are no longer sent with 1xx or 204 responses

selected by the server. New in version 5.1. ### 6.3 HTTP servers and clients ##### 6.3.1 tornado.httpserver — Non-blocking HTTP server ## A non-blocking, single-threaded HTTP server Typical applications httpclient • The io_loop argument to all AsyncHTTPClient constructors has been removed. ### tornado.httpserver • It is now possible for a client to reuse a connection after sending a chunked request. 5.3 Jan 6, 2018 ### tornado.curl\_httpclient • Improved debug logging on Python 3. ### tornado.httpserver • Content-Length and Transfer-Encoding headers are no longer sent with 1xx or 204 responses

be called with the future when it is ready. ### 4.3 HTTP servers and clients ##### 4.3.1 tornado.httpserver — Non-blocking HTTP server A non-blocking, single-threaded HTTP server. Typical applications Tornado 4.5.3 Jan 6, 2018 tornado.curl\_httpclient • Improved debug logging on Python 3. tornado.httpserver • Content-Length and Transfer-Encoding headers are no longer sent with 1xx or 204 responses new proxy_auth_mode argument. • The minimum supported version of libcurl is now 7.22.0. ### tornado.httpserver • HTTPServer now accepts the keyword argument trusted_downstream which controls the parsing

selected by the server. New in version 5.1. ### 6.3 HTTP servers and clients ##### 6.3.1 tornado.httpserver — Non-blocking HTTP server A non-blocking, single-threaded HTTP server. Typical applications httpclient • The io_loop argument to all AsyncHTTPClient constructors has been removed. ### tornado.httpserver • It is now possible for a client to reuse a connection after sending a chunked request. Tornado 4.5.3 Jan 6, 2018 tornado.curl\_httpclient • Improved debug logging on Python 3. ### tornado.httpserver • Content-Length and Transfer-Encoding headers are no longer sent with 1xx or 204 responses

selected by the server. New in version 5.1. ### 6.3 HTTP servers and clients ##### 6.3.1 tornado.httpserver — Non-blocking HTTP server A non-blocking, single-threaded HTTP server. Typical applications httpclient • The io_loop argument to all AsyncHTTPClient constructors has been removed. ### tornado.httpserver • It is now possible for a client to reuse a connection after sending a chunked request. Tornado 4.5.3 Jan 6, 2018 tornado.curl\_httpclient • Improved debug logging on Python 3. ### tornado.httpserver • Content-Length and Transfer-Encoding headers are no longer sent with 1xx or 204 responses

selected by the server. New in version 5.1. ### 6.3 HTTP servers and clients ##### 6.3.1 tornado.httpserver — Non-blocking HTTP server A non-blocking, single-threaded HTTP server. Typical applications httpclient • The io_loop argument to all AsyncHTTPClient constructors has been removed. ### tornado.httpserver • It is now possible for a client to reuse a connection after sending a chunked request. Tornado 4.5.3 Jan 6, 2018 tornado.curl\_httpclient • Improved debug logging on Python 3. ### tornado.httpserver • Content-Length and Transfer-Encoding headers are no longer sent with 1xx or 204 responses

selected by the server. New in version 5.1. ### 6.3 HTTP servers and clients ##### 6.3.1 tornado.httpserver — Non-blocking HTTP server A non-blocking, single-threaded HTTP server. Typical applications httpclient • The io_loop argument to all AsyncHTTPClient constructors has been removed. ### tornado.httpserver • It is now possible for a client to reuse a connection after sending a chunked request. 3 ## Jan 6, 2018 ### tornado.curl\_httpclient • Improved debug logging on Python 3. ### tornado.httpserver • Content-Length and Transfer-Encoding headers are no longer sent with 1xx or 204 responses