radosgw swift: error messages: spurious newline after http body causes weird errors.
The swift support in go (github.com/ncw/swift) is pickier about http, it checks for incorrect behavior and complains, as is its right.
The swift support in radosgw emits spurious newlines after errors. Actually, it seems to do it for success too. Not sure if the newline is ever a good idea, but if it is, it should be properly accounted for when setting "content-length". If the newline is a bad thing, then it needs to go away. There's some thought that the newline should be a crlf, which is possible but a strict reading of RFC 2616 suggests this shouldn't be a strict requirement.
This bug isn't visible using curl, because everything looks "correct" until the client tries to read past the end of the output from the request, and curl doesn't do that. Apparently the python swift code also doesn't care.
I tested with 'master', but the bug may have been there since 2013 and I think was originally reported in jewel.
#4 Updated by Nathan Cutler 3 months ago
- Status changed from Need Review to Pending Backport