Created attachment 1211237 [details] Wireshark showing \n instead of \r\n at end of 404 response Description of problem: The Go (1.7.1) language net.http library is strict and is throwing an error when an extra \n is returned by the radosgw. We can find the extra \n at the end of a 404. Please see the attached image. Steps to Reproduce: 1. Access a 404 response from the radosgw 2. See the extra \n at the end of the response. Actual results: \n is an invalid ending, causing an error in strict language libraries. In Go's net.http library the following error is seen: Unsolicited response received on idle HTTP channel starting with "\n"; err=<nil> Expected results: \r\n would be considered valid.
Fix merged to upstream as commit 5f229d6a33eae4906f22cdb90941835e47ee9f02 Author: Marcus Watts <mwatts> Date: Wed Jan 11 00:06:15 2017 -0500 radosgw/swift: clean up flush / newline behavior. Scheduled for jewel backport.
Verified on 10.2.5-27
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2017-0514.html