Bugfix: Incorrect ordering of newline and carriage return in HTTP server

The HTTP server was printing "\n\r" at the end of lines in the response
headers, which is invalid and caused some HTTP clients to detect an end
to the headers after the first header line.

The server now prints the proper "\r\n" sequence, which is parsed
correctly by clients.
Merge branch 'master' of github.com:InvictusInnovations/fc