Errata

Print Print Icon

Submit your own errata for this product.


The errata list is a list of errors and their corrections that were found after the product was released.

The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.

Color Key: Serious Technical Mistake Minor Technical Mistake Language or formatting error Typo Question



Version Location Description Submitted By
Printed Page f
Send HTTP

should be:

(g) Send HTTP

And the unlabelled return message should be labelled:

 Anonymous 
Printed Page f
Returns IP address 207.25.71.5

This is probably obvious from the context.

 Anonymous 
Printed Page 57
Figure 3-11

The caption is incorrect. All of the traffic is HTTP 1.1 with no
protocol upgrade taking place.

 Anonymous 
Printed Page 76
First paragraph and figure 4-3(b)

In the paragraph text the cryptographic encryption layer is identified as "TLS or
SSL". In part b of figure 4-3 it is identified as "TSL or SSL". I believe the
correct version of the acronym is TLS (not TSL). It stands for Transport Layer
Security.

 Anonymous 
Printed Page 83
5th paragraph

"Frequently, the disabled acknowledgement algorithms introduce significant delays."
should read:
Frequently, the delayed acknowledgement algorithms introduce significant delays."

 Anonymous 
Printed Page 84
6th paragraph

The third line of paragraph six has the following:
"Second, Nagle's algorithm interacts poorly with disabled acknowledgments.."

"disabled" should be replaced with "delayed"

 Anonymous 
Printed Page 149
figure 6-17

While reviewing the sample chapter 6 in PDF, which is available online, l have found
a mistake in figure 6-17, maybe due to the fact that it seems to be a retouch of
figure 6-16 that appears in the previous section.

The mistake is as follows: point (3a) is repeated twice in the
figure, but the one on the lower left corner is mistaken, and should
be removed. In fact, its legend "The browser does auto-expansion,
converting 'oreilly' into 'www.oreilly.com'" is also incorrect, as
the starting paragraph of this section states that "[...] the browser
no longer performs any of these convenience expansions [...]".

Nevertheless, there is no point in correcting the legend, because
both the point (3a) and its legend should be removed from figure
6-17.

Another possibility which might also work would be to change the number of this point
to (1b) and modify its legend as follows (copied from the paragraph immediately above
the figure): "The browser adds the default scheme and path but leaves the hostname as
entered, thus converting 'oreilly' into 'http://oreilly/'".

 Anonymous 
Printed Page 152
First example text under the Via Syntax section

is:
Via = 1.1 cache.joes-hardware.com, 1.1 proxy.irenes-isp.net
should be:
Via: 1.1 proxy-62.irenes-isp.net, 1.0 cache.joes-hardware.com

 Anonymous 
Printed Page 152
The "Via" syntax, second example text, needs improvement.

is:
Via = "Via" ":" 1#( waypoint )
should be:
Via = "Via" ":" ( waypoint )[", " ( waypoint )...]

 Anonymous 
Printed Page 154
Privacy and security implications of Via

There are some cases where we want don't want exact hostnames

should be:

There are some cases where we don't want exact hostnames

 Anonymous 
Printed Page 191
2nd footnote

of even of short-lifetime objects.

should be:

of even short-lifetime objects.

 Anonymous 
Printed Page 192
Figure 7-18

The label 'time_got_response' should be moved one node to the right,
and the currently labelled node should be removed from the Cache
timeline.

 Anonymous 
Printed Page 195
Log Migration

some large cache providers have been know

should be:

some large cache providers have been known

 Anonymous 
Printed Page 221
Figure 8-13

Normal SLL connection

should be:

Normal SSL connection

 Anonymous 
Printed Page 347
Item 6

This item does not really relate to determining entity body length,
and in fact the text of this item is repeated in the following
paragraph. Nevertheless, the text of this item is more correct than
that of the following paragraph.

So the following paragraph should be striken, and the item number
should be removed from this item so that the text of this item
replaces the following paragraph.

 Anonymous 
Printed Page 357
Figure 15-6.

Page 357 Figure 15-6. Anatomy of a chunked message.

According to the http RFC point 3.6.1
[http://www.ietf.org/rfc/rfc2616.txt]
there should be an extra CRLF at the end of the figure.

Chunked-Body = *chunk
last-chunk
trailer
CRLF



 Anonymous 
Printed Page 363
1st paragraph

even thought the

should be:

even though the

 Anonymous 
Printed Page 402
5th paragraph

varaint

should be:

variant

 Anonymous 
Printed Page 431
last paragraph

lock taken.

should be:

lock token.

 Anonymous 
Printed Page 441
last sentence

403 locked,

should be:

423 locked,

 Anonymous 
Printed Page 449
3rd paragraph

incoming messages must somehow be somehow among the servers

should be:

incoming messages must somehow be distributed amongst the servers

 Anonymous 
Printed Page 453
1st paragraph

combination with some of the other redirection technique.

should be:

combination with one or more of the other redirection techniques.

 Anonymous 
Printed Page 458
Figure 20-4

Anonymous 
Printed Page 466
2nd paragraph

Dynamic Host Discovery Protocol

AFAIK this does not exist as described, and should be:

Dynamic Host Configuration Protocol

 Anonymous