views:

55

answers:

2
+2  A: 

This is HTTP Chunked transfer encoding, If you don't want to get that, do an HTTP 1.0 request instead.

Hasturkun
+5  A: 

The server is using "chunked" encoding, which allows the web server to keep HTTP connections open for reuse after a request for a dynamically generated page (e.g. CGI, PHP, or ASP), without buffering the entire page at the server end before transmission. It works by sending small parts ("chunks") of the web page at a time that each have a specified length in bytes (the hexadecimal numbers you see scattered throughout the page). That allows the client to know when the server is done sending data.

Per RFC 2616 (the HTTP specification), all HTTP/1.1 clients are required to be able to decode chunked encoding. This means that if you do not want to receive a chunked response, you will need to request the page using the version identifier of HTTP/1.0, an older version of the specification:

telnet www.mysite.com 80
GET / HTTP/1.0
Host: www.mysite.com 

The server will then close the connection after it has finished responding instead of using chunked encoding and keeping the connection open.

idealmachine