keystone/keystone/token
Morgan Fainberg 82101a36d3 HEAD responses should return same status as GET
According to the HTTP spec, a HEAD request should return the same
status and headers as the GET request (including content-type and
content-length). The HEAD request simply strips out the body and
returns no body. Any case where HEAD routing returned a different
status code than GET, now returns the same status and headers.

Any case where HEAD was supported where GET was not supported now
supports both GET and HEAD.

The wsgi.render_response code now handles HEAD appropriately and
will maintain headers while enforcing no body data is returned.

The bulk of this change is to support the same behavior between
deploying Keystone under eventlet and under HTTPD + mod_wsgi. In
the case of deploying under HTTPD + mod_wsgi, there are cases
where mod_wsgi will turn a HEAD request into a GET request to
ensure that the proper response is rendered. With these changes
all HEAD responses will respond in the same manner under either
eventlet or mod_wsgi.

Change-Id: I13ce159cbe9739d4bf5d321fc4bd069245f32734
Closes-Bug: #1334368
2014-07-08 22:37:44 -07:00
..
backends remove unneeded definitions of Python Source Code Encoding 2014-06-08 16:44:45 +00:00
providers Consolidate provider calls to token_api.create_token 2014-06-27 13:46:59 -05:00
__init__.py Safer noqa handling 2014-03-27 18:52:07 -05:00
controllers.py HEAD responses should return same status as GET 2014-07-08 22:37:44 -07:00
core.py Configurable token hash algorithm 2014-04-09 19:27:39 -05:00
provider.py Default to PKIZ tokens 2014-06-17 17:25:28 -07:00
routers.py HEAD responses should return same status as GET 2014-07-08 22:37:44 -07:00