Message266996
Patched the behaviors when NO_CONTENT and RESET_CONTENT are sent via send_error(). According to RFCs, they aren't actually errors so sending them through send_response() seems to make the most sense, however.
send_error()'s behavior changes in this patch are:
- Removed content-length field in the header for NO_CONTENT as per the RFC
- Removed content-length field in the header for RESET_CONTENT also to comply with option c) mentioned in RFC7321 6.3.6 |
|
Date |
User |
Action |
Args |
2016-06-03 00:01:12 | Susumu Koshiba | set | recipients:
+ Susumu Koshiba, martin.panter, deronnax, spaceone |
2016-06-03 00:01:12 | Susumu Koshiba | set | messageid: <1464912072.14.0.263239539505.issue25738@psf.upfronthosting.co.za> |
2016-06-03 00:01:12 | Susumu Koshiba | link | issue25738 messages |
2016-06-03 00:01:12 | Susumu Koshiba | create | |
|