Zamez.org NetSurf HTTP Lint Factor CSS RUfl Sargasso EarthData

HTTP Lint

for web developers · web interface, Linux

Httplint performs various checks on HTTP/1.1 headers returned by a server.

It checks the syntax and content of almost all HTTP/1.1 response headers, and also warns about missing headers and suggests improvements.

C source · RISC OS application (482K) · Browse CVS

Results for http://www.askapache.com/seo/wp-plugin-search-engine-verify.html

• HTTP/1.1 200 OK[0d][0a]
  • A response status code in the range 200 - 299 indicates that the request was successful.
• Date: Thu, 29 Jul 2010 16:21:21 GMT[0d][0a]
  • OK.
• Server: Apache[0d][0a]
  • OK.
• X-Pingback: http://www.askapache.com/xmlrpc.php[0d][0a]
  • This is an extension header. I don't know how to check it.
• Link: <http://www.askapache.com/?p=270>; rel=shortlink[0d][0a]
  • Warning: I don't know anything about this header. Is it a standard HTTP response header?
• Cache-Control: public,max-age=29030400[0d][0a]
  • OK.
• Vary: Accept-Encoding[0d][0a]
  • OK.
• Transfer-Encoding: chunked[0d][0a]
  • OK.
• Content-Type: text/html; charset=UTF-8[0d][0a]
  • OK.
• Content-Language: en[0d][0a]
  • OK.
• [0d][0a]
  • End of headers.

• No Last-Modified header was present. The HTTP/1.1 specification states that this header should be sent whenever feasible.
• This URL appears to contain implementation-specific parts such as an extension or a query string. This may make the URL liable to change when the implementation is changed, resulting in broken links. Consider using URL rewriting or equivalent to implement a future-proof URL space. See http://www.w3.org/Provider/Style/URI for more information.