Maybe a simple solution is to follow the redirection. For the example given (and similarly in my case), "w3m -dump_extra http://users.skynet.be/dummy/" reports that the page is redirected to http://hostingerrors.isp.belgacom.be/Errors.cgi?url=http://users.skynet.be/dummy/ but then that page has the proper head :
$ w3m -dump_head http://users.skynet.be/dummy/ HTTP/1.1 404 Not Found Date: Sat, 29 Mar 2008 16:03:43 GMT Server: Apache/1.3.33 (Debian GNU/Linux) mod_ssl/2.8.22 OpenSSL/0.9.7e Connection: close Content-Type: text/html
Maybe a simple solution is to follow the redirection. For the example given (and similarly in my case), "w3m -dump_extra http:// users.skynet. be/dummy/" reports that the page is redirected to http:// hostingerrors. isp.belgacom. be/Errors. cgi?url= http:// users.skynet. be/dummy/ but then that page has the proper head :
$ w3m -dump_head http:// users.skynet. be/dummy/
HTTP/1.1 404 Not Found
Date: Sat, 29 Mar 2008 16:03:43 GMT
Server: Apache/1.3.33 (Debian GNU/Linux) mod_ssl/2.8.22 OpenSSL/0.9.7e
Connection: close
Content-Type: text/html