Version 4.1 - 3.1 HTTP
This section should not be a problem. I've done a LOT of captures of HTTP traffic and subsequent analysis. If you've never done this, you probably should. It's a good way to see the "guts" of HTTP. Use a wired connection to your home router and capture packets on that interface as you're browsing web sites. Then analyze the packets - click one of the HTTP packets and "follow tcp stream." It will show you all the parts that you see in a HTTP session. If you need assistance with this, the Wireshark HTTP page is a really good resource.
"The Hyper Text Transport Protocol is a text-based request-response client-server protocol." It normally runs on port 80, but can run on non-standard ports. I'm not sure how much of the "history" will be important. But you should probably know the request methods:
* GET
* HEAD
* POST
* PUT
* DELETE
* TRACE
* OPTIONS
* CONNECT
* PATCH
"Some of the methods (for example, HEAD, GET, OPTIONS and TRACE) are, by convention, defined as safe, which means they are intended only for information retrieval and should not change the state of the server." Note that the methods are in ALL CAPS. You should probably know the response codes too - or at least the major groupings:
1XX Informational
2XX Success
3XX Redirection
4XX Client Error
5XX Server Error
So you will normally get a response of 200 - OK or 404 - Not Found or 500 Internal Server Error to a GET request. If you know all of this - along with User Agents, URIs, URLs and MIME types, you should be good for this section. Note that there are a lot of MIME types, but the ones relevant to HTTP can be found on this handy Mozilla developer page.
As far as security goes, HTTP is not secure. HTTPS is the secure version of HTTP.