Change http_keepalive default value from True to False
Bug #1433435 reported by
Abhishek Kekane
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Glance |
Invalid
|
Medium
|
Abhishek Kekane |
Bug Description
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.
Right now it is set to True for backward compatibility.
Changed in glance: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in glance: | |
assignee: | nobody → Satyanarayana Patibandla (satya-patibandla) |
Changed in glance: | |
assignee: | Satyanarayana Patibandla (satya-patibandla) → Abhishek Kekane (abhishek-kekane) |
milestone: | none → kilo-3 |
Changed in glance: | |
status: | Confirmed → In Progress |
Changed in glance: | |
milestone: | kilo-3 → kilo-rc1 |
tags: | added: kilo-rc-potential |
Changed in glance: | |
milestone: | kilo-rc1 → none |
tags: | removed: kilo-rc-potential |
Changed in glance: | |
status: | In Progress → Invalid |
summary: |
- Change http_keepalive default value from Ture to False + Change http_keepalive default value from True to False |
To post a comment you must log in.
Hi Satynarayana,
I have already pushed a patch for review to address this issue.
Not sure why LP is not updated for the same.
Please refer, https:/ /review. openstack. org/#/c/ 165321/ 1