chunked transfer client disconnect causes unhandled value error in object server
Bug #667956 reported by
clayg
This bug affects 7 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Object Storage (swift) |
Fix Released
|
Low
|
Unassigned |
Bug Description
If a client disconnects while the object-server is expecting the chunk length line on a chunked transfer - it blows up.
This may need to be patched upstream:
Oct 28 13:05:22 saio object-server STDOUT: File "/usr/local/
Oct 28 13:05:22 saio object-server STDOUT: self.chunk_length = int(rfile.
Oct 28 13:05:22 saio object-server STDOUT: ValueError: invalid literal for int() with base 16: ''
... or mabye we can catch it.
Changed in swift: | |
milestone: | 1.2.0 → 1.2-rc |
Changed in swift: | |
milestone: | 1.2-rc → 1.3.0 |
Changed in swift: | |
milestone: | 1.3.0 → none |
Changed in swift: | |
status: | New → Confirmed |
Changed in swift: | |
assignee: | nobody → Tong Li (litong01) |
Changed in swift: | |
milestone: | none → next-kilo |
Changed in swift: | |
status: | Fix Committed → Fix Released |
Changed in swift: | |
milestone: | 2.3.0-rc1 → 2.3.0 |
To post a comment you must log in.
It would be nice if it raised something more selective upstream. But we should be able to catch it by putting a try/except (ValueError, IOError) around the request. body_file. read loop.