Errata

WebSocket

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

Version Location Description Submitted By Date submitted Date corrected
Printed, PDF, ePub
Page chapter 2: ebook listing of client.html
html script entry at bottom of example

At the end of the HTML script example for client.html it shows the following script entry:

<script src="http://bit.ly/maxcdn-bootstrap-js" ></script >

Lombardi, Andrew (2015-09-09). WebSocket: Lightweight Client-Server Communications (Kindle Locations 358-359). O'Reilly Media. Kindle Edition.

However, the link to "maxcdn-bootstrap-js" returns a 403 error "Forbidden". Using the full length link contained in the author's git repo for chapter 2 works correctly:

<script src="http://maxcdn.bootstrapcdn.com/bootstrap/3.2.0/js/bootstrap.min.js"></script>

Note from the Author or Editor:
In order to fix, you can use the full URL which reader has identified from the git repo: http://maxcdn.bootstrapcdn.com/bootstrap/3.2.0/js/bootstrap.min.js

or I've created a new bitly URL which should be updated in later revisions to fix:

http://bit.ly/maxcdn-bootstrapjs

Anonymous  Dec 22, 2015 
PDF
Page 37
1st and 3rd paragraph

The bitly links on page 37 to STOMP 1.0 Protocol Docs go to a bitly warning page.

Note from the Author or Editor:
The error is showing up because someone at the URL shortening service bitly.com incorrectly marked the shortened URL as potentially problematic. The full URL is: http://stomp.github.io/stomp-specification-1.0.html and should be entered if you're worried about seeing this problem message in the future. bitly has been contacted to see if they can have that error resolved on their end.

blimmer  Apr 17, 2016