What problems does pageVault solve?
• Knowing exactly what content your web site delivered to every request pageVault archives all novel responses, whether static html, dynamic html generated from Perl, cgi-bin, servlets, scripts, server-side includes, databases or any other method, images, documents, sounds, … So, for example, dynamically generated responses to search queries are archived equally with responses to requests for the home page. Every unique response is archived. • Providing a history of how your web site looked at a certain date and time pageVault provides easy access to the archive based on URL or date/time. You can see how your site looked at any date/time since you started running pageVault. You can see how a page changed, and even replay the evolution of a page over time, seeing changes down to the byte level exactly as they were sent from the web server to you site’s visitors.
• Knowing exactly what content your web site delivered to every request pageVault archives all novel responses, whether static html, dynamic html generated from Perl, cgi-bin, servlets, scripts, server-side includes, databases or any other method, images, documents, sounds, … So, for example, dynamically generated responses to search queries are archived equally with responses to requests for the home page. Every unique response is archived. • Providing a history of how your web site looked at a certain date and time pageVault provides easy access to the archive based on URL or date/time. You can see how your site looked at any date/time since you started running pageVault. You can see how a page changed, and even replay the evolution of a page over time, seeing changes down to the byte level exactly as they were sent from the web server to you site’s visitors. • Backup and recoverability of content As a side-effect of archiving every distinct response sent by your webserver, pageVau
