[SRU] webob last stable version 1.1.1 response header bug
Bug #920197 reported by
peter.pang
This bug affects 8 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-webob (Ubuntu) |
Fix Released
|
High
|
Chuck Short | ||
Precise |
Fix Released
|
High
|
Chuck Short | ||
Quantal |
Fix Released
|
High
|
Chuck Short | ||
swift (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Precise |
Won't Fix
|
Undecided
|
Unassigned | ||
Quantal |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
if u use webob last stable version 1.1.1 with swift and want to send a HEAD request to get an object info,
the response http header CONTENT-TYPE and CONTENT-LENGTH will be wrong,
it should return the real content type and real length of the object like: image/gif , 139520 (bytes)
but it just return text/html and all http header length
the real stable version i test is 1.0.8
thanks
Related branches
Changed in python-webob (Ubuntu): | |
importance: | Undecided → High |
status: | New → Confirmed |
Changed in python-webob (Ubuntu Quantal): | |
assignee: | nobody → Chuck Short (zulcss) |
Changed in python-webob (Ubuntu Precise): | |
assignee: | nobody → Chuck Short (zulcss) |
Changed in swift (Ubuntu Precise): | |
status: | New → Confirmed |
summary: |
- webob last stable version 1.1.1 response header bug + [SRU] webob last stable version 1.1.1 response header bug |
Changed in python-webob (Ubuntu Precise): | |
milestone: | none → ubuntu-12.04.1 |
Changed in swift (Ubuntu Precise): | |
milestone: | none → ubuntu-12.04.1 |
Changed in swift: | |
status: | New → Confirmed |
tags: | added: rls-q-incoming |
Changed in swift (Ubuntu Precise): | |
status: | Confirmed → Triaged |
Changed in swift (Ubuntu Precise): | |
milestone: | ubuntu-12.04.1 → none |
Changed in python-webob (Ubuntu Precise): | |
status: | Triaged → In Progress |
To post a comment you must log in.
The bug shows up in functional tests, this particular case triggers it:
nosetests test.functional .tests: TestFile. testHead
We have traced it down to this change in WebOb made on Jun 30 2011, shortly after 1.0.8 was released: /github. com/Pylons/ webob/commit/ 2e23e221ff85eac 81623ff7a07b1a6 30ae263ec9
https:/
"make sure WSGIHTTPException return the same headers for HEAD and GET requests"
It appears that a contributing factor is that Swift uses exceptions even for successful results, such as webob.exc.HTTPOk. The erroneous content-type and content-length correspond to the textual representation of the HTTPOk "exception".