Only change timeout to 100ms after the connection is established.

tests/standalone/io/http_server_idle_timeout_test.dart

Index: tests/standalone/io/http_server_idle_timeout_test.dart
diff --git a/tests/standalone/io/http_server_idle_timeout_test.dart b/tests/standalone/io/http_server_idle_timeout_test.dart
index 91e164c7aacf3d7f75ddec254ba4bd28303a74e5..fbbf0647c006d339b37e8c635d6ab870d31a96a6 100644
--- a/tests/standalone/io/http_server_idle_timeout_test.dart
+++ b/tests/standalone/io/http_server_idle_timeout_test.dart
@@ -7,7 +7,6 @@
 // VMOptions=--short_socket_write
 // VMOptions=--short_socket_read --short_socket_write
 
-import "package:expect/expect.dart";
 import "dart:async";
 import "dart:io";
 import "dart:isolate";
@@ -15,11 +14,11 @@ import "dart:isolate";
 
 void testTimeoutAfterRequest() {
   HttpServer.bind("127.0.0.1", 0).then((server) {

[Søren Gjesse, 2013/08/21 07:39:54]

Set server.idleTimeout to null here for completeness.

[Anders Johnsen, 2013/08/21 07:43:49]

Done.

-    server.idleTimeout = const Duration(milliseconds: 100);
 
     server.listen((request) => request.response.close());
 
     Socket.connect("127.0.0.1", server.port).then((socket) {

[Søren Gjesse, 2013/08/21 07:39:54]

How about waiting with timer until response data has been received? The call to
write could be delayed as well.

[Anders Johnsen, 2013/08/21 07:43:49]

If I wait so long, the timer would already be started with a 'null' timer, thus
being disabled. Moving to server.listen though.

+      server.idleTimeout = const Duration(milliseconds: 100);
       var data = "GET / HTTP/1.1\r\nContent-Length: 0\r\n\r\n";
       socket.write(data);
       socket.listen(