What Prof.Harris Taught

1. We went to http://www.cs.tut.fi/~jkorpela/http.html to look at HTTP headers.
2. We looked at Authorization, Cache-Control, Connection (must not be communicated by proxies over further connection), Content- Encoding (), Content ? Language, Content-Length (Most important, tells you roughly how long it is), Content-Location (Tells where the actual source is) and many of such.
3. The two most important ones are Content-Type and Content-Length.
4. It is always save to say application/octet in content-type.
5. Showed different instances oh header definition: http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html
6. If the content-coding of an entity in a request message is not acceptable to the origin server, the server SHOULD respond with a status code of 415
7. He talked about forward-fill-finish.
8. He tried to put light as what will happen after HTTP.
9. He discussed the title: ?PHP HTTP POST Incorrect MIME Header Parsing Vulnerability?.
10. MIME can call itself. It is like a content handler rather than a protocol handler.

What I Learned

I read RFC2616 to understand HTTP header field definitions.

Code links

Listings