make IOError exceptions during POST data read() easy to identify
|Reported by:||dlowe||Owned by:||nobody|
|Cc:||grahamd, carljm||Triage Stage:||Ready for checkin|
|Has patch:||yes||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
In short, I want to be able to suppress the IOError exceptions that are raised under common, but completely uncontrollable, client conditions e.g. connection abruptly closed. Like others, though, I find it unacceptable to completely suppress IOError exceptions, though -- it's a very broad exception class, and I don't want to hide real bugs.
The attached patch addresses this by catching IOErrors that occur while read()ing POST data, and re-throwing them as a new subclass of IOError.
Cc: grahamd and carljm, who are associated with the other two tickets.
Change History (8)
Changed 4 years ago by dlowe
comment:1 Changed 4 years ago by aaugustin
- Needs documentation unset
- Needs tests unset
- Patch needs improvement unset
- Triage Stage changed from Unreviewed to Design decision needed
comment:3 Changed 4 years ago by carljm
- Patch needs improvement set
- Triage Stage changed from Design decision needed to Accepted