diff options
Diffstat (limited to 'test/simple/test-http-wget.js')
| -rw-r--r-- | test/simple/test-http-wget.js | 18 |
1 files changed, 9 insertions, 9 deletions
diff --git a/test/simple/test-http-wget.js b/test/simple/test-http-wget.js index 98ea43fc20..56372256a1 100644 --- a/test/simple/test-http-wget.js +++ b/test/simple/test-http-wget.js @@ -4,17 +4,17 @@ http = require("http"); // wget sends an HTTP/1.0 request with Connection: Keep-Alive // -// Sending back a chunked response to an HTTP/1.0 client would be wrong, -// so what has to happen in this case is that the connection is closed -// by the server after the entity body if the Content-Length was not +// Sending back a chunked response to an HTTP/1.0 client would be wrong, +// so what has to happen in this case is that the connection is closed +// by the server after the entity body if the Content-Length was not // sent. // -// If the Content-Length was sent, we can probably safely honor the -// keep-alive request, even though HTTP 1.0 doesn't say that the -// connection can be kept open. Presumably any client sending this -// header knows that it is extending HTTP/1.0 and can handle the -// response. We don't test that here however, just that if the -// content-length is not provided, that the connection is in fact +// If the Content-Length was sent, we can probably safely honor the +// keep-alive request, even though HTTP 1.0 doesn't say that the +// connection can be kept open. Presumably any client sending this +// header knows that it is extending HTTP/1.0 and can handle the +// response. We don't test that here however, just that if the +// content-length is not provided, that the connection is in fact // closed. var server_response = ""; |