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

Fix errors spotted by jturnball.

Browse Source
This commit is contained in:
Paul J. Davis 2010-12-12 18:12:33 -05:00
parent 2e39db265c
commit 80594c5442
2 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
doc/htdocs/faq.html
View File

@ -65,8 +65,9 @@ machine. See the <a class="reference external" href="/configure.html#proc-name">
<div class="section" id="why-is-there-no-http-keep-alive"> <div class="section" id="why-is-there-no-http-keep-alive">
<h3><a class="toc-backref" href="#contents">Why is there no HTTP Keep-Alive?</a></h3> <h3><a class="toc-backref" href="#contents">Why is there no HTTP Keep-Alive?</a></h3>
<p>The default Sync workers are designed to run behind Nginx which only uses <p>The default Sync workers are designed to run behind Nginx which only uses
HTTP/1.0 with it's upstream servers. If you want to send requests directly HTTP/1.0 with its upstream servers. If you want to deploy Gunicorn to
to Nginx you should use one of the various async workers.</p> handle unbuffered requests (ie, serving requests directly from the internet)
you should use one of the async workers.</p>
</div> </div>
</div> </div>
<div class="section" id="worker-processes"> <div class="section" id="worker-processes">

5
doc/site/faq.rst
View File

@ -53,8 +53,9 @@ Why is there no HTTP Keep-Alive?
-------------------------------- --------------------------------
The default Sync workers are designed to run behind Nginx which only uses The default Sync workers are designed to run behind Nginx which only uses
HTTP/1.0 with it's upstream servers. If you want to send requests directly HTTP/1.0 with its upstream servers. If you want to deploy Gunicorn to
to Nginx you should use one of the various async workers. handle unbuffered requests (ie, serving requests directly from the internet)
you should use one of the 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