1. The "shopping cart" interface on an online store might be a series
of requests from the user to go to product pages and add items to cart.
Part of the response would be an update to the shopping cart and on
something like Amazon, the indicator in the corner telling you how many
items are currently in your cart. I feel like the product page would
bet a GET and adding an item to cart would be a POST? I'm not sure
how the readout on the site itself would be handled, whether by GET or
a different method entirely.
2. So the specifics of what things like "X-Content-Type-Options" and
"X-Frame-Options" actually mean are still foreign to me, but it makes sense
that navigating a page, interacting with elements on a page, and anything
else in that vein would involve some method of communicating between the
client and the server. Looking at this now, I can see why GET and POST are
the most common methods used in HTTP requests.
Chris Proctor
Pat Wick
pwick