Don't report unuseful SocketIOExceptions on HttpServer.

Don't report unuseful SocketIOExceptions on HttpServer.

1) Don't report error if HttpResponse was closed while we were sending
data. Instead, just drain/close the data sources. This matches how
people expect the HttpResponse to act. This will _not_ happen for
HttpClientRequest.

2) Don't report incomplete headers on HttpServer.listen. The information
are not useful, as the user don't even have a chance to act on the bad
headers/socket. We not just silently close the socket.

BUG=
R=sgjesse@google.com

Committed: https://code.google.com/p/dart/source/detail?r=23069

[Søren Gjesse, 2013-05-23 13:48:15]

lgtm

LGTM

https://codereview.chromium.org/15814004/diff/1/tests/standalone/io/http_serv...
File tests/standalone/io/http_server_response_test.dart (right):

https://codereview.chromium.org/15814004/diff/1/tests/standalone/io/http_serv...
tests/standalone/io/http_server_response_test.dart:141: write() {
Maybe interleave the addStream calls with some StringSink calls.

[Anders Johnsen, 2013-05-23 13:54:50]

https://codereview.chromium.org/15814004/diff/1/tests/standalone/io/http_serv...
File tests/standalone/io/http_server_response_test.dart (right):

https://codereview.chromium.org/15814004/diff/1/tests/standalone/io/http_serv...
tests/standalone/io/http_server_response_test.dart:141: write() {
On 2013/05/23 13:48:15, Søren Gjesse wrote:
> Maybe interleave the addStream calls with some StringSink calls.

Done.

[Anders Johnsen, 2013-05-23 13:55:24]

Committed patchset #2 manually as r23069 (presubmit successful).