Notice that you have to hit the RETURN key twice before you see the HTML. If you can scroll backwards to the HTTP/1.0 command you gave, you'll see the HTTP/1.0 "Response Headers". Have a look though them, noting theGET /home/index.html HTTP/1.0
Content-length:
, Content-type:
and the various date-related headers.
telnet proxy.latrobe.edu.au 8080
. Once
connected, the GET command is the same as usual except you request a
full URL, eg:
In fact, from within La Trobe this is the only way you can access Web pages outside the university. Can you tell if the page you fetch was cached at the proxy server?GET http://www.unimelb.edu.au HTTP/1.0<newline><newline>
/usr/local/etc/httpd/ironbark/logs/access_log
,
/usr/local/etc/httpd/ironbark/logs/referer_log
and
/usr/local/etc/httpd/ironbark/logs/agent_log
. These files
are usually huge, so the easy way to look at your own
stuff is to use the Unix grep
utility to extract the lines
you're interested in. For example, I use the following to see who's
reading my (pscott's) Web pages:
A few words of explanation: thegrep -v latrobe /usr/local/etc/httpd/ironbark/logs/access_log | grep pscott | less +G
grep -v latrobe
only selects records (ie, lines) which don't contain the
string "latrobe" -- I'm interested in accesses from outside La Trobe.
The result of this is piped into a second grep
which selects only those lines containing the string "pscott", as all
references to my Web pages do.
You can copy-and-paste this command into a text file on Unix, run
chmod a+x
on the file to make it executable, and
use it as a command to check your own logs -- changing "pscott" to your
own username, naturally. You can do similar things with the
referrer_log
file. The
agent_log
file is a bit different -- it simply
lists the browser ID for each access. It's still worth a look.