RU beehive logo ITEC dept promo banner
ITEC 325
2017spring
ibarland

homelectshws
D2Lbreeze (snow day)

client-and-server-2
intro: web requests and responses

recall: So, the essence of the situation is that the server and browser are functions with the type-signatures:
server: stringurl → stringhtml
browser: stringhtml → void.
The above is a lie. Let's look more closely.

Looking more closely

For this class, you'll need a browser with good debug-tools built in. For Firefox, there is an extension “Firebug”; I'll demo a couple of Chrome's built-in tools. We will not worry about supporting old browers (e.g. old versions of IE).

» More Tools » Developer Tools
We'll look briefly at the "Elements" tab, but today we're mostly concerned with the "Network" tab, and clicking on particular files. In particular, viewing the Request Headers and Response Headers.

Together in class: Spend 15min looking at examples.

Btw, here are the official HTTP response codes, or the cat-picture version.

the real upshot: So, the essence of the situation is actually that the server and browser are functions with the type-signatures:
server: http-request-packet → http-response-packet (where the first packet contains the URL, and the second packet contains the html response);
browser: http-response-packet → void.

Further things to consider (if not today, then perhaps later:)

homelectshws
D2Lbreeze (snow day)


©2017, Ian Barland, Radford University
Last modified 2017.Jan.29 (Sun)
Please mail any suggestions
(incl. typos, broken links)
to ibarlandradford.edu
Rendered by Racket.