Change http_keepalive default value from True to False

Bug #1433435 reported by Abhishek Kekane
6
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.

Tags: ntt
Zhi Yan Liu (lzy-dev)
Changed in glance:
status: New → Confirmed
importance: Undecided → Medium
Changed in glance:
assignee: nobody → Satyanarayana Patibandla (satya-patibandla)
Revision history for this message
Abhishek Kekane (abhishek-kekane) wrote :

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

Zhi Yan Liu (lzy-dev)
Changed in glance:
assignee: Satyanarayana Patibandla (satya-patibandla) → Abhishek Kekane (abhishek-kekane)
milestone: none → kilo-3
Changed in glance:
status: Confirmed → In Progress
Thierry Carrez (ttx)
Changed in glance:
milestone: kilo-3 → kilo-rc1
tags: added: kilo-rc-potential
Changed in glance:
milestone: kilo-rc1 → none
Thierry Carrez (ttx)
tags: removed: kilo-rc-potential
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on glance (master)

Change abandoned by Abhishek Kekane (<email address hidden>) on branch: master
Review: https://review.openstack.org/165321

Changed in glance:
status: In Progress → Invalid
Tushar Patil (tpatil)
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.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.