Errata

Designing Evolvable Web APIs with ASP.NET

Errata for Designing Evolvable Web APIs with ASP.NET

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 Note Update

Version Location Description Submitted by Date submitted
PDF Page ix
Using Code Examples

The link for code examples is probably incorrect : https://github.com/oreillymedia/title_title

Where can I download Code Examples ?

Anonymous  Mar 06, 2014 
Printed Author Bios

Pablo's bio should read "Pablo is an internationally recognized expert with over 14 years of experience in designing and implementing large distributed systems with Microsoft technologies and a Connected System MVP.
For the last 9 years Pablo has helped numerous Microsoft teams develop tools and frameworks for building service-oriented applications with Web Services, ASP.NET and Windows Communication Foundation (WCF).
Pablo now focuses on technologies that enable developers to build large scale systems and web applications with focus on mobile, such as HTML5, Node.js, ASP.NET or Windows Azure."

Nicole  Apr 11, 2014 
Printed Some figure captions

Some captions in Darrel's chapters refer to colors in figures; figs are black and white in print version.

Nicole  Apr 11, 2014 
PDF Page 9
1st paragraph, 3rd line

"The request is then set to an HTTP server"

The word "set" should probably actually be "sent"

Anonymous  Sep 19, 2013 
PDF, Mobi Page 9
Figure 1-4 and Figure 1-5 on Page 10

The entity body in the two figures list the "Name" at "Jane User", but rather than a close quote to "Jane User", there is a colon.

Bernard Chen  Apr 22, 2014 
PDF Page 10
last paragraph

The line: "HTTP is a transport protocolit provides in addition to data extra control information" is missing a space bewteen words. The word "protocolit" should be "protocol it"

Sixto  Jan 07, 2014 
PDF Page 12
PUT - paragraph

There is a missing period in this line: "sentation,
it should return a 200(OK) or a 204 (No Content) However, if the resource". It should be added at "204 (No Content)." phrase.

Sixto  Jan 07, 2014 
PDF Page 13
2nd bullet of Conditional Requests paragraph

The text: "A conditional PUT is where a client sends headers with the server can use to determine
if the client?s cached representation is still valid. If it is, the server returns a 409 (Preconditions Failed)." contains two errors. The word "with" should be "which". The phrase "If it is," should be "If it is not valid," to be correct technically.

Sixto  Jan 07, 2014 
PDF Page 20
1st paragraph

It seems the section header markup was not converted. This line: "tingham.
==== Authentication ==== HTTP provides an extensible framework (http://" should likely be the start of a new section.

Sixto  Jan 07, 2014 
PDF Page 20
2nd bullet of Authenticaton Schemes paragraph

The line: "thentication.html) involves the client concatenating several parts of eh request to" has a type. The word "eh" should be "the".

Sixto  Jan 07, 2014 
PDF Page 25
First line of Guidelines for Web APIs section

There is an extra word "set" in this line: "Below are set a set of guidelines that differentiate Web APIs from other forms of API."

Sixto  Jan 07, 2014 
ePub Page 25
Table 1-1. Http methods

According to Table 1-1. Http methods PATCH is idempotent. According to RFC 5789 (https://tools.ietf.org/html/rfc5789) PATCH is not idempotent.

Christoph Rosenberger  Jan 18, 2017 
PDF Page 39
3rd paragraph

The word "makes" is missing from the line: "However Paypal documention explains the rel and this it is possible to navigate the" between the words "this it". Also, the word "documention" should be "documentation",

Sixto  Jan 07, 2014 
Printed Page 41
First line in "REST Constraints" section

Reads: "Rest defines the following six constraints....", but there are 10 constraints listed.

Anonymous  Oct 29, 2015 
PDF Page 59
United States

Example code for GreetingController shows a method named "GetGreeting." For the routing to work correctly, this method should simply be named "Get"

Pedro  Aug 30, 2014 
Printed Page 69
Figure 4-1

The block pointed to "Route Dispacther Message Handler" should have the text "Route resolution" and not "Controller selection"

Nicole  Apr 11, 2014 
PDF Page 97
2nd paragraph

The line: "this information is that it primarily just human readable. It does not tend to affect the" is missing the word "be" between "primarily just".

Sixto  Jan 08, 2014 
PDF Page 123
3rd paragraph

The line: "create a link relation that uses a URI. However, URIs can be long an noisy in represen-" mistakenly uses the word "an" instead of "and".

Sixto  Jan 09, 2014 
PDF Page 129
2nd paragraph

The line: "internet. Once a new type has been let out onto the internet there is guaranteed way of" is missing the word "no" between "is guaranteed".

Sixto  Jan 09, 2014 
PDF Page 129
3rd paragraph

There line: "specification be published on the internet and an announcement of desire to submit bee" uses the word "bee" instead of "be".

Sixto  Jan 09, 2014 
PDF Page 130
1st paragraph

The line: "type. There three distinct paths that you could take when doing this." is missing the word "are" between "There three".

Sixto  Jan 09, 2014 
PDF Page 130
4th paragraph

The line: "and am prepared to use them in other scenarios. Hopefully as more people adopt the" misuses the word "am" it should use "and are prepared"

Sixto  Jan 09, 2014 
PDF Page 131
1st paragraph

The line: "interesting example is sitemap(http://microformats.org/wiki/rel-sitemap) which a wide" is missing the word "is" between "which a".

Sixto  Jan 09, 2014 
PDF Page 131
2nd paragraph

The line: "to be a URI. The enables the use of the domain naming system to ensure uniqueness." misuse the word "the". It should be "This enables the use".

Sixto  Jan 09, 2014 
PDF Page 171
1st Paragraph, 2nd Bullet

The GitHub link to Manos is incorrect. It should be:
https://github.com/jacksonh/manos

Paul Smith  Jul 01, 2013 
PDF Page 171
1st Paragraph, 1st Bullet

Missing link for more information on Firefly. Currently reads:

Firefly: Written by Louis Dejardin. Firefly is a very light bare bones HTTP server.

could be:

Firefly (http://loudej.github.io/firefly/): Written by Louis Dejardin. Firefly is a very light bare bones HTTP server.

Paul Smith  Jul 01, 2013 
PDF Page 171
1st paragraph, line 1 and 2

The Line "Sending a request to ?http://localhost:8080? using an accept header of ?application/ vnd.image+json? is not consitent with the Figure 8-2. The URI should be http://localhost:8080/issue and the accepte-header "application/vnd.issue+json".

Josef Eissing  Jan 29, 2014 
PDF Page 171
1st paragraph, line 1 and 2

The Line "Sending a request to ?http://localhost:8080? using an accept header of ?application/ vnd.image+json? is not consitent with the Figure 8-2. The URI should be http://localhost:8080/issue and the accepte-header "application/collection+json".

Josef.Eissing  Jan 29, 2014 
PDF Page 320
United States

* ModelBindingParameterBinder should be HttpParameterBinding (http://msdn.microsoft.com/en-us/library/system.web.http.controllers.httpparameterbinding(v=vs.118).aspx)

* FormatterParameterBinder should be FormatterParameterBinding (http://msdn.microsoft.com/en-us/library/system.web.http.modelbinding.formatterparameterbinding(v=vs.118).aspx)

Chris Simmons  Mar 26, 2014 
PDF Page 324
4th para

ModelBindingContent should be ModelBindingContext (http://msdn.microsoft.com/en-us/library/system.web.mvc.modelbindingcontext(v=vs.118).aspx)

Chris Simmons  Mar 26, 2014 
Mobi, Page 351
United States

In example 14-4 (Pluggable response handler), in the ApplyResponseHandler method, the variable named "response" is declared again inside the loop, despite already existing as a method parameter.

As a result, the reader can't tell what the actual intended behavior of the method should be.

James Nail  Jun 17, 2015 
PDF Page 476
Portugal

On "Figure D-4. Client B does a conditional PUT", the HTTP Response from the Origin should have a new ETag. It returns the same ETag.

Fernando Nunes  Mar 19, 2015