Using Wera in combination with a Proxy server will take care of some of the redirect issues. Work still remains for determining which issues are handled and which are not (for the 0.4.2 release)

For further details see 0.4.1 release notes

The advanced search has not been prioritized for this release. Functionality needed not specified.

Canonization of URLs is now added. If a link points to an URL that is indexed with a different form (e.g http://www.nb.no instead of http://nb.no), WERA will now find this in the index. Canonicalization is configurable. Induvidual rules may be disabled, an the order in which the rules are applied may be changed.

The Javascript inserted by WERA before the html page is delivered to the users browser does not catch all links. To prevent this undesired behaviour the web server hosting WERA can be set up as Proxy server so that all requests for other hosts than the WERA host can be redirected back to WERA. Of course, the user will have to change the browsers proxy setting so that all requests goes to the WERA host.

Currently, no canonization of URLs is done in WERA. If a link points to an URL that is indexed with a different form (e.g http://www.nb.no instead of http://nb.no), WERA will not find this in the index and therefore will report: Sorry, no documents with the given uri were found. See [1312202] exacturl needs to canonicalize.

WERA does nothing to handle redirects. The result, depending on the nature of the redirect, will be either that the actual resource is not displayed at all in WERA or that a redirect to live web is executed within the WERA view without any information to the user See bugtracker issues [1312200] Pages at end of redirects not found and [1312214] More redirects to live web.

The advanced search has not been prioritized for this release. Functionality needed not specified.

The old index_encode algorithm used for encoding urls in Wera has been replaced by PHP's native urlencode function. See [1354276] Still have URL encoding issues and [1247134] Beautify the wera URL.

Possibility to display metadata from the Retriever's getmeta request. A metadata check box has been added to the time line view. When checked, the metadata shows up below the timeline (instead of the archived web page).

The presentation of results has been changed so that the default view is one hit per site. Each hit has a link to 'more from this site' which presents all hits within that site in the same was as the old wera result list.

Currently, no canonization of URLs is done in WERA. If a link points to an URL that is indexed with a different form (e.g http://www.nb.no instead of http://nb.no), WERA will not find this in the index and therefore will report: Sorry, no documents with the given uri were found. See [1312202] exacturl needs to canonicalize.

WERA does nothing to handle redirects. The result, depending on the nature of the redirect, will be either that the actual resource is not displayed at all in WERA or that a redirect to live web is executed within the WERA view without any information to the user See bugtracker issues [1312200] Pages at end of redirects not found and [1312214] More redirects to live web.

The advanced search has not been prioritized for this release. Functionality needed not specified.

The handling of exacturl searches has been improved considerably on both WERA and NutchWax side. WERA uses the exacturl search functionality extensively both for counting versions of a given URL and to determine the mapping between a given URL/timestamp and its Arc name and offset.

WERA's error messages has been improved. Instead of printing cryptical PHP warnings and errors it prints more meaningful error messages enabling to user to understand what is wrong.

There were major problems with querying with non-ISO8859 characters. To solve this issue changes were made to both WERA and NutchWax.

WERA now sets the encoding in the header of a given web page prior to sending the page to the users browser. The encoding sent is the encoding detected by NutchWax at index time.