Apache Request and Response Headers
Most users don't realise that while browsing the WWW there is a constant conversation going on between the browser and the web server. Below you can see the specific Headers that were passed from your browser to our webserver and back when this page was requested.
Apache Request Headers
The following headers were sent by your browser when requesting this page:
| Header | Value |
|---|---|
| x-cc-id | ccc02-01 |
| If-Modified-Since | Fri, 02 Apr 2010 13:35:15 GMT |
| Host | www.the-art-of-web.com |
| User-Agent | CCBot/1.0 (+www.commoncrawl.org/bot.html) |
| Accept | text/html,application/xhtml+xml,text/xml;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 |
| Accept-Language | en-us,en;q=0.5 |
| Accept-Encoding | gzip |
| Accept-Charset | ISO-8859-1,utf-8;q=0.7,*;q=0.7 |
| Connection | close |
| Cache-Control | no-cache |
| Pragma | no-cache |
Output produced by the PHP function apache_request_headers.
Apache Response Headers
Our server sent the following headers in response to your request:
| Header | Value |
|---|---|
| Last-Modified | Sun, 22 Nov 2009 13:36:13 GMT |
Output produced by the PHP function apache_response_headers.
Related Articles
References
User Comments and Notes
26 September 2008: Bernhard Schulte says:
Actually your Apache did not send what your page says, but rather sent headers spilling the beans about the patchlevel of your OpenSSL install.
This page displays only the headers that were sent by your browser with the request, and those returned from our server by Apache - not the other server headers that you are referring to. But thanks for the tip, you'll find that those headers are now blocked (as they should be) by a ServerTokens directive 
