HTTP Pocket Reference
by Clinton Wong

Unconfirmed error reports are from readers.  They have not yet been 
approved or disproved by the author or editor and represent solely the
opinion of the reader.

This page was updated June 16, 2003.

Here's a key to the markup:

        [page-number]: serious technical mistake
        {page-number}: minor technical mistake
        <page-number>: important language/formatting problem
        (page-number): language change or minor formatting problem
        ?page-number?: reader question or request for clarification


UNCONFIRMED errors and comments from readers:


{2} section headed by ":80":
Ports are associated with TCP/UDP, not IP, correct? You'll never find a part 
in the header of an IP packet for a port number. That's taken care of in the 
TCP packet headers. So perhaps the sentence:

"The port number can be any legitimate IP port number:..." should read "The 
port number can be any legitimate TCP port number..."


(8) footnote:

	Use of HTTP 1.1 is encourage over 1.0 

should read

	Use of HTTP 1.1 is encouraged over 1.0


[12] Example:
The example for HEAD command uses the same example as the GET command so it 
doesn't do what the HEAD command should do.


{40,48} under Content-Language and Accept-Language language tags:
Delete "two-letter".  RFC 3066 allows for language tags of any length.  
(Example: i-klingon, az-cyrillic, wen, sgn-US, zun).



(72)  Request Header Lines;
The header values for Connection: Keep-Alive and Connection: Close are shown in
proper case (Close, and Keep-Alive).

The RFC shows them as lower case, as does the information on page 34.

This inconsistency is also present on pages 3, 11, and 13.