rainbows.git - Unicorn for sleepy apps and slow clients

Date	Commit message (Collapse)
2011-01-07	redirect unexpected test output to /dev/null
	We check the return code anyways, and spewing random binary data to the terminal with verbosity on is not a good idea.
2011-01-05	tests: ensure 416 responses do keepalive
	This is useful for clients that specify a bad range, we can preserve the connection for them to specify a good response.
2011-01-05	send proper 416 responses
	416 responses without a body should respond with a zero Content-Length and a Content-Range that allows clients to specify a proper range in the future. rfc2616, section 14.16 says: > A server sending a response with status code 416 (Requested > range not satisfiable) SHOULD include a Content-Range field > with a byte-range- resp-spec of "*". The instance-length > specifies the current length of the selected resource.
2011-01-04	return 206 status for partial sendfile responses
	Although curl did not complain, 206 is the correct error code for partial HTTP responses.
2011-01-04	coolio_thread_*: fix 416 response handling
	After beefing up and enabling byte range tests for "sendfile" (and no just IO.copy_stream), we noticed threaded-Coolio variants did not handle invalid byte ranges correctly.