Keystone API is forcing Content-Transfer: chunked on responses
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
Wishlist
|
Dolph Mathews |
Bug Description
Hi,
I'am implementing CORS support for Keystone. Everything is working except that on response I'am setting Content-Length header to 0 but response is sent to user using Tramsfer-Encoding: chunked.
Code added to PublicRouter class:
# Cors Operations
CorsCotroller class is as follows:
class CorsController(
def __init__(self):
def get_options(self, context):
headers = [('Access-
return wsgi.render_
Everything seems to be working:
echo -e 'OPTIONS /v2.0/tokens HTTP/1.1\r\n' | nc 10.76.0.206 5000
HTTP/1.1 200 OK
Access-
Access-
Access-
Access-
Content-Type: text/html; charset=UTF-8
Date: Thu, 21 Jun 2012 17:52:29 GMT
Transfer-Encoding: chunked
0
B
Changed in keystone: | |
milestone: | folsom-2 → none |
milestone: | none → folsom-3 |
Changed in keystone: | |
status: | Fix Committed → Fix Released |
Changed in keystone: | |
milestone: | folsom-3 → 2012.2 |
I'm not sure it's fair to qualify this as a "bug" considering you're logging it against new development that hasn't been committed... but the "solution" is to provide webob with a complete response object.