lwp-request -esd 'http://www.postgresql.org/files/documentation/books/pghandbuch/html/sql-createindex.html'
200 OK
Connection: close
Date: Sun, 09 Jan 2005 02:27:42 GMT
Accept-Ranges: bytes
Age: 135
ETag: "7398c5-2c7f-41e08228"
Server: Apache/1.3.31 (Unix) PHP/4.3.9 mod_ssl/2.8.20 OpenSSL/0.9.7d
Content-Length: 11391
Content-Type: text/html; charset=utf-8
Last-Modified: Sun, 09 Jan 2005 01:00:24 GMT
Client-Date: Sun, 09 Jan 2005 02:29:57 GMT
Client-Peer: 66.98.251.159:80
Client-Response-Num: 1
Link: <mailto:pgsql-docs@postgresql.org>; rev="MADE"
Link: <index.html>; rel="HOME"; title="PostgreSQL"
Link: <sql-commands.html>; rel="UP"; title="SQL-Befehle"
Link: <sql-creategroup.html>; rel="PREVIOUS"; title="CREATE GROUP"
Link: <sql-createlanguage.html>; rel="NEXT"; title="CREATE LANGUAGE"
Link: <stylesheet.css>; rel="STYLESHEET"; type="text/css"
Title: CREATE INDEX
X-Cache: HIT from nme-pow-pr3.tpgi.com.au
X-Meta-Creation: 2003-05-26T21:48:18
X-Meta-GENERATOR: Modular DocBook HTML Stylesheet Version 1.73
Notice how the server replies with content-type text/html; charset=utf-8 when in fact, it's NOT encoded in utf8.....
If you return charset in content type, then it better be in that charset, or browsers will get confused, not to mention
searchengines will have a hard time indexing it.
Kind regards,
John