There is a strict rule about constructing status line for HTTP:
'...Status-Line, consisting of the protocol version followed by a
numeric status code and its associated textual phrase, with each
element separated by SP characters'
(http://www.faqs.org/rfcs/rfc2616.html)
This patch ensures an associated textual phrase for a status code
is always written in the HTTP response.
Reviewed: https:/ /review. openstack. org/223235 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=dbda82afd8a c0ae4373ea35d99 0e124bbac91eef
Committed: https:/
Submitter: Jenkins
Branch: master
commit dbda82afd8ac0ae 4373ea35d990e12 4bbac91eef
Author: Marian Horban <email address hidden>
Date: Mon Sep 14 13:43:36 2015 -0400
Fix Status-Line in HTTP response
There is a strict rule about constructing status line for HTTP: .Status- Line, consisting of the protocol version followed by a www.faqs. org/rfcs/ rfc2616. html)
'..
numeric status code and its associated textual phrase, with each
element separated by SP characters'
(http://
This patch ensures an associated textual phrase for a status code
is always written in the HTTP response.
Closes-Bug: #1496055 1eb032d23d7b16a a2bf2c0bb73
Change-Id: I68d4c41d0c0487