jingrow/gunicorn
1
0
Fork 0
mirror of https://github.com/frappe/gunicorn.git synced 2026-01-14 11:09:11 +08:00
Code Issues Packages Projects Releases Wiki Activity

Slight rewording for the Keep-Alive FAQ.

Browse Source
This commit is contained in:
Paul J. Davis 2010-12-12 12:07:25 -05:00
parent 73d7e906a9
commit 7f800c0eeb
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/site/faq.rst
View File

@ -49,12 +49,12 @@ Gunicorn fails to start with upstart
Make sure you run gunicorn with ``--daemon`` option. Make sure you run gunicorn with ``--daemon`` option.
HTTP keep-alive? Why is there no HTTP Keep-Alive?
---------------- --------------------------------
HTTP keep-alive is usually managed by the proxy on top of gunicorn (like The default Sync workers are designed to run behind Nginx which only uses
NGINX). If Gunicorn is serving directly requests to the internet, you HTTP/1.0 with it's upstream servers. If you want to send requests directly
need to use one of the async workers. See the design_ page for more info. to Nginx you should use one of the various async workers.
.. _slowloris: http://ha.ckers.org/slowloris/ .. _slowloris: http://ha.ckers.org/slowloris/
.. _setproctitle: http://pypi.python.org/pypi/setproctitle .. _setproctitle: http://pypi.python.org/pypi/setproctitle