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. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Corrected".

The following errata were submitted by our customers and approved as valid errors by the author or editor.


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



Version Location Description Submitted By Corrected
Printed Page xviii
4th paragraph, last sentance

"this book will show you to do it" should read "this book will show you how to do it"

Anonymous 
Printed Page xix

"It shows" -> "We show"

Anonymous 
Printed Page 5.5.3
2nd to last paragraph

Paragraph has double quotes after the '4' that should be removed:
In Section 5.4"

Corresponds to page 123 of print book. Problem is only in Safari version.

Anonymous 
Printed Page 13

"Starting in chapter 5" -> "Starting in chapter 4"
"In Resource-Oriented Architectures" -> "In resource-oriented architectures"


Anonymous 
Printed Page 17

"Split the Data Set into Resources [115]" -> "chapter 5"

Anonymous 
Printed Page 17
2nd Paragraph, 1st Sentance

"happen to live into the URI portion" should read "happen to live in the URI portion"

Anonymous 
Printed Page 18

"a RESTful web services" -> "a RESTful web service"

Anonymous 
Printed Page 27

"under same rules" -> "under the same rules"

Anonymous 
Printed Page 28

The sentences starting "The del.icio,.us web service sends back..." should go between example 2-2 and example 2-3.

Anonymous 
Printed Page 31

The sentence "I've added two keyword arguments to open: :method" is
confusing because there are two colons next to each other, and it
looks like a Ruby method called open::method. Rephrase to "I've added
two keyword arguments to open. They are :method..."

Strike the line "require 'rubygems'" from example 2-4.

Anonymous 
Printed Page 35
top third of page

/**
* A command-line application that fetches bookmarks from del.icio.us
* and prints them to strandard output.
*/

strandard --> standard

Anonymous 
Printed Page 38

"Basic HTTP, GET, and POST" -> "Basic HTTP GET and POST"

Anonymous 
Printed Page 45

Example 2-3; the line between the two "alert" calls should not be indented any more than the lines that surround it. That is,

alert(
json =
alert(

Anonymous 
Printed Page 49

"defects the RPC style" -> "defects to the RPC style"

Anonymous 
Printed Page 51

"Object.value=" -> "S3Object.value="

Anonymous 
Printed Page 55

"39 official HTTP" -> "41 official HTTP"

Anonymous 
Printed Page 58

"Now, as shown in Example 3-6, let's write the S3::Bucket class,"
->
"Now, let's write the S3::Bucket class (Example 3-6),"

Anonymous 
Printed Page 65

"This is a job for public-key cryptography" -> "S3 solves this problem using a message authentication code (MAC)".

your "private" key (remember, not truly private: Amazon knows it too)"
->
your secret key (remember, the secret is shared between you and Amazon)

Only someone with the "private" key
->
Only someone who knows the secret

revealing your "private" key
->
revealing the secret

know your "private" key
->
know your secret

Anonymous 
Printed Page 66

signs it (again, Amazon has a copy of your "private"key)
->
signs it (again, Amazon knows your secret key)

Anonymous 
Printed Page 82

"in Preface" -> "in the Preface"

Anonymous 
Printed Page 83

"Name the Resources" section. -> "Name the Resources" section of chapter 5.

Anonymous 
Printed Page 88
Figure 4-1

Two of the arrows in Figure 4-1 are wrong. The arrow going from
"Initial State" to "'mice', page 2" should have a solid line and be
labeled "Request". The arrow going back from 'mice', page 2" to
"Initial State" should have a dotted line and be labeled "Response".

Anonymous 
Printed Page 89 and many other pages - do a global search (11 times total)
Line 2

"neccessary" -> "necessary"

Anonymous 
Printed Page 89

"start=50, and" -> "start=500, and"

The two sentence beginning "However, there is something unRESTful"
should be put into parentheses or made into a footnote. "The Trouble
with Cookies" should include a reference to the chapter in which it's
found: chapter 8.

Anonymous 
Printed Page 89
Third complete paragraph

"addressabile" -> "addressable"

Anonymous 
Printed Page 90

"bits of client state" -> "bits of application state"

"process it" -> "process the request"

"That's client state:" -> "That's application state:"

Anonymous 
Printed Page 90
last paragraph, 3rd sentence

"and the server restricts" -> "and the server"

Anonymous 
Printed Page 91
Last paragraph

"unneccessary" -> "unnecessary"

Anonymous 
Printed Page 95
1st paragraph

cache of the extrenal page
=>
cache of the external page

Anonymous 
Printed Page 98

"saw the HEAD method" -> "You saw the HEAD method"

Anonymous 
Printed Page 101

"accepts POST requests" -> "accepts a POST request"

Anonymous 
Printed Page 102

"Multiplying by any other number" -> "Multiplication by any other number"

Anonymous 
Printed Page 103

"50" -> "-50"

Anonymous 
Printed Page 109-110

. The given procedure for turning requirements into read-only resources is exactly the same as the procedure given in chapter 6. It
should be a slightly simpler procedure. As printed, steps 4 and 6 are
unnecessary for read-only resources. They should be omitted. The
procedure should have seven steps as follows:

1. Figure out the data set
2. Split the data set into resources

For each kind of resource:

3. Name the resources with URIs
4. Design the representation(s) served to the client
5. Integrate this resource into existing resources, using hypermedia
links and forms
6. Consider the typical course of events: what's supposed to happen?
7. Consider error conditions: what might go wrong?

> resources is exactly the same as the procedure given in chapter 6. It
> should be a slightly simpler procedure. As printed, steps 4 and 6 are
> unnecessary for read-only resources. They should be omitted. The
> procedure should have seven steps as follows:

Correction to the correction: steps 4 and _5_ are the unneccesary ones.

Anonymous 
Printed Page 112
Split the Data Set into Resources, first paragraph, 3rd line

Anything that might be refereed to by name ought...
should be:
Anything that might be refered to by name ought...

Anonymous 
Printed Page 121

The footnote should be attached to "detailed", not "get."

Anonymous 
Printed Page 125
Example 5-3

[{url="http://maps.example.com/Earth,description="Earth"},
{url="http://maps.example.com/Venus,description="Venus"},

should have quotes after the text of each URL:

[{url="http://maps.example.com/Earth",description="Earth"},
{url="http://maps.example.com/Venus",description="Venus"},

Anonymous  Jan 2009
Printed Page 128, 129

Both figures should say "(Image data courtesy Google Maps")

Anonymous 
Printed Page 129

"directly to the east" -> "the part directly to the east"

Anonymous 
Printed Page 148

"steps 3 and 4" -> "steps 4 and 5"

Anonymous 
Printed Page 167

"ang architecture" -> "an architecture"

Anonymous 
Printed Page 176
mid page

"if you know one you can calculate the other" -> "if you know the
former you can calculate the latter".

Anonymous 
Printed Page 179

The last sentence of the section "The Leftovers" contains a redundant "of".

Anonymous 
Printed Page 183
Example 7-4

All the end tags are </body>, rather than matching the opening tag.

Should be:
<full-name>Leonard Richardson</full-name>
<email>leonardr@example.com</email>
<password>mypassword</password>

Anonymous 
Printed Page 184
General Note, 1st paragraph

...reimplements something you can already, do...

should be

...reimplements something you can already do...

(without comma)

Anonymous 
Printed Page 187

The last sentence of the 4th paragraph missed a period at the end of the sentence after "more generally".

Anonymous 
Printed Page 201
the second sentence in the last paragraph

"I can get this data fairly easily with ActiveResource, and format it as a representation with to_xml__but what about security__?"

There should be a comma before "but what about security".

Anonymous 
Printed Page 202
Example 7-20, The second line the of comment

This PUT handler is a little __tricker__ than others, ....

should be "trickier" actually.

Anonymous 
Printed Page 217
Third line of fourth paragraph

"Atome" -> "Atom"

Anonymous 
Printed Page 219

see "Overloading POST -> see "Overloading POST" below

Anonymous 
Printed Page 235

The sentence starting "Except for the protocol change..." should be in
parentheses.

Anonymous 
Printed Page 237

"URI templates" -> "URI Templates"

Anonymous 
Printed Page 248

"about it use" -> "about its use"

Anonymous 
Printed Page 249

"If the client then..." -> "If a client"

"from resource is" -> "from http://www.example.com/resource is"

Anonymous 
Printed Page 254
the last sentence

put this token the Authorization header -> put this token in the
Authorization header

Anonymous 
Printed Page 259
the first sentence of the last paragraph

A new line should be inserted after the Media type line.

Anonymous 
Printed Page 262 (and also on page 2)
Paragraph following "rel-nofollow" line

"neccessarily" -> "necessarily"

Anonymous 
Printed Page 271

The sentence starting "The Universal Encoding..." should be a footnote or else put in parentheses.

Anonymous 
Printed Page 272

"if you're using UTF-16" -> "UTF-16"

Anonymous 
Printed Page 274
5th paragraph, last sentence

WRONG: "...should now result in a response code of 310 ("Moved Permanently")..."
RIGHT: "...should now result in a response code of 301 ("Moved Permanently")..."

Anonymous 
Printed Page 285

'https://s3.amazonaws.com/, and then the bucket name' should be in quotes.

Anonymous 
Printed Page 289

"content type" should be "media type" throughout.

Anonymous 
Printed Page 292

Indentation in example 9-10 is off. The second <doc> tag should be
beneath its enclosing <param> tag, and the <resource path="recent"> tag
should be beneath its enclosing <resource> tag.

Anonymous 
Printed Page 293

Similarly for Example 9-11. The <doc> tags should be indented beneath their enclosing <param> tags.

Anonymous 
Printed Page 307

"It abstracts away" -> "They abstract away"

Anonymous 
Printed Page 317

"this next." -> "this later."

Anonymous 
Printed Page 322

"The chart below has the details, but"
Strike. There is no chart.

Anonymous 
Printed Page 331

Paragraph "There's also an insecure method" should be in parentheses.

Anonymous 
Printed Page 340

"GET, POST, and/or DELETE" -> "GET, PUT, and/or DELETE"

Anonymous 
Printed Page 341

"six standard methods" -> "five standard methods"

also

"PUT /weblogs/{ID}: Delete a weblog"
"PUT" should be "DELETE"

Anonymous 
Printed Page 365

"few resources of your own" -> "few new resources"

Anonymous 
Printed Page 384

"their request" -> "the request"

Anonymous 
Printed Page 394

"popular response header" -> "popular request header"

Anonymous 
Printed Page 396
Second paragraph

"take the value of Expires should as a rough guide" -> "take the value of Expires as a rough guide".

Anonymous 
Printed Page 396

"described next" -> "described later"

Anonymous 


"Every IT generation has its seminal tome that transcends time and connects the dots in a way that no book had before it...RESTful Web Services will be, in my opinion, that book for the 2000s Web services generation."
--Thomas Beck, Beckshome.com: Thomas Beck's Blog