Inspecting WebSocket Traffic - The Definitive Guide to HTML5 WebSocket - page 167

•

chrome://omnibox

•

chrome://plugins

•

chrome://policy

•

chrome://predictors

•

chrome://profiler

•

chrome://quota-internals

•

chrome://settings

•

chrome://stats

•

chrome://sync-internals

•

chrome://terms

•

chrome://tracing

•

chrome://version

chrome://print
In the address bar, type chrome://net-internals . One use of net-internals is to
inspect TCP socket events. These TCP sockets are used to transport WebSocket and
other protocols used by the browser for communication. When you click Sockets on the
left, Chrome displays the socket pools. What we're interested in is the currently active,
live sockets, so click the View live sockets link. In a separate window or tab, open the
WebSocket Echo test at http://www.websocket.org/echo.html , and click Connect.
A new entry shows up right away, along with the following URL: ws://echo.websocket.
org/?encoding=text . Click the entry, and on the right, you'll see the network internals,
as shown in Listing A-4.

•

Listing A-4. Network Internals of a WebSocket Handshake

830: SOCKET
ws://echo.websocket.org/?encoding=text
Start Time: 2012-11-23 20:08:27.489

t=1353730107489 [st= 0] +SOCKET_ALIVE [dt=?]
--> source_dependency = 828 (SOCKET_STREAM)
t=1353730107489 [st= 0] +TCP_CONNECT [dt=91]
--> address_list = ["174.129.224.73:80"]
t=1353730107489 [st= 0] TCP_CONNECT_ATTEMPT [dt=91]
--> address = "174.129.224.73:80"
t=1353730107580 [st= 91] -TCP_CONNECT
--> source_address = "10.0.1.5:57878"
t=1353730107582 [st= 93] SOCKET_BYTES_SENT
--> byte_count = 470
t=1353730107677 [st=188] SOCKET_BYTES_RECEIVED
--> byte_count = 542