Although mod_tidy makes the impression of being a validator, it isn't one mod_tidy is just a handy and comfortable tool to help make web documents being valid.
mod_tidy is a TidyLib based DSO module for the Apache HTTP Server Version 2 to parse, clean-up and pretty-print the webservers' (X)HTML output.
Web documents which pass mod_tidy's severe checks – what means, that they don't run into an error page – can be called valid and well-formed (depends on mod_tidy's configuration, the default is severe).
So prepared, they easily pass a validation check like the W3C Markup Validation Service, which marks the reference validating tool of its kind. If you regulary control the quality of your Web documents with mod_tidy, the use of an obligatory validation check can more be seen as an optional free exercise.
How does it work?
mod_tidy works as a filter that hooks up to the (X)HTML output of an Apache 2 webserver. It passes the webservers' (X)HTML output to TidyLib which parses and optional cleans-up and pretty-prints that output. If TidyLib detects an error, the client receives a HTML page with a list of all found errors and warnings that prevent the input of being a valid (X)HTML document. If TidyLib doesn't complain, the client will get and display the (X)HTML data as without mod_tidy.
Due to the fact that mod_tidy may affect little response delays of the webserver, its use should be reduced to a developer framework only. mod_tidy is not recommended to be used in a production environment, where response delays of the webserver are undesirable.
Who makes it?
mod_tidy is initially written by Sebastian Tusk, who has retired from that project. The previous official project page has been accessible through the web for years, until it has been silently closed in April 2005. With kindly permission of the initial project owner, Sierk Bornemann has created a new home on Sourceforge.net to give mod_tidy a new chance.
· Apache 2.x