Why does the viewer require a dedicated servlet container?
The pageVault Viewer allows you to browse requests delivered by the archived web sites at “a point in time”. To do this, the pageVault Viewer tries to alter every URL on pages it retrives from the Archiver to include a timestamp and a prefix which will send the request back to the Viewer. This means that when you click on a hyperlink in a web page shown by the viewer, the request is handled by the Viewer which retrieves the relevant response from the archive. But a problem arises for URL’s which pageVault cannot alter, such as those generated by javascript running within the delivered page. Attempting to interpret the javascript and alter it appropriately is not a viable approach. So, occasionally a request for a page will be made which does not include the expected prefix and timestamp. The pageVault viewer attempts to guess the timestamp by inspecting the referer header received with the request. However, these requests will have arbitrary URLs, hence, the servlet environment must be
