8e7a0dbb12
Presently, the wsgi server allows persist connections. Hence even after the response is sent to the client, it doesn't close the client socket connection. Because of this problem, the green thread is not released back to the pool. In order to close the client socket connection explicitly after the response is sent and read successfully by the client, you simply have to set keepalive to False when you create a wsgi server. Added a parameter to take advantage of the new(ish) eventlet socket timeout behaviour. Allows closing idle client connections after a period of time, eg: $ time nc localhost 8776 real 1m0.063s Setting 'client_socket_timeout = 0' means do not timeout. DocImpact: Added wsgi_keep_alive option (default=True). Added client_socket_timeout option (default=900). SecurityImpact Closes-Bug: #1361360 Change-Id: I3a361d6590d1800b85791f23ac1cdfd79815341b |
||
|---|---|---|
| .. | ||
| init.d | ||
| neutron | ||
| api-paste.ini | ||
| dhcp_agent.ini | ||
| fwaas_driver.ini | ||
| l3_agent.ini | ||
| lbaas_agent.ini | ||
| metadata_agent.ini | ||
| metering_agent.ini | ||
| neutron.conf | ||
| policy.json | ||
| rootwrap.conf | ||
| services.conf | ||
| vpn_agent.ini | ||