Sneaky Pete
--#--
When I was in junior high school, some buddies and I used to think it 
fun to hang around after school until everyone but the custodial staff had 
left. We'd find an unlocked window and break <i>back into</i> school. <br>
<br>
I'm sure that's evidence of my lack of a life in adolescence, but it was 
quite a thrill to poke through the empty classrooms and explore the girls' 
bathrooms. <br>
<br>
What I'm going to show you has that same thrilling spector of tamely illicit 
adventure. Though there's really no harm, or even rules against what we're 
about to do, it still seems like we're sneaking back into school with no one 
knowing.<br>
<br>
We're going to surf the 'Net manually, without aid of browser. The main point 
of this exercise is to get a good grasp of exactly how the HTTP protocol works.<br>
<br>
These days there are plenty of Webmasters who <i>think</i> they understand the 
HTTP protocol, but do they really? Do you? <br>
<br>
Do you understand how a Web browser makes a request for a page, or sends 
posted information to a CGI program or Java servlet? I suggest you read 
the official documents that define how it's done and are required reading 
for anyone wishing to build a browser or Web server. HTTP 1.0 is defined by 
<a href="http://www.w3.org/Protocols/rfc1945/rfc1945">RFC1945</a> and the 
new HTTP 1.1 is defined by <a href="ftp://ftp.isi.edu/in-notes/rfc2616.txt">RFC2616</a>.<br>
<br>
These documents are the <i>authoritative</i> sources on how browsers and servers 
are supposed to behave. But first, let's do some sneaking around. 
<br>