Re: [Archive-access-discuss] missing port number in wayback 1.0.1 search results

[Chris V. <cv...@gm...>]

Just a little update. I was able to get this to work in Wayback 0.8.0 (which
we are still using in a production app). The ResultURIConverter class was
extended and the makeReplayUri(SearchResult) method was overridden to use
the RESULT_URL_KEY (which contains port information) to form the replay URI
(instead of the RESULT_URL). The JSReplayRenderer class was also extended so
that the <base href. ..> tag and the javascript sResourceUrl variable also
use the RESULT_URL_KEY value.

After minimal testing, this seems to work without breaking any existing
functionality.  Does anyone know of a scenario where this will not work?

Eventually, once we move to Wayback 1.0.1, similar changes will need to be
made there.

-Chris

On Feb 4, 2008 3:19 PM, Chris Vicary <cv...@gm...> wrote:

> Hi all,
>
> I am having a problem retrieving harvested resources whose urls include
> port numbers using Wayback 1.0.1. We have a seed that includes a port
> number that was harvested using heritrix. The resulting arc files were
> indexed using wayback, and the urls stored in the index include the port
> number. Using the wayback web address search interface, I am able to find
> the urls by including the port number in the search string (if the port
> number is not included, no results are found - which is expected). The link
> for the search result does not include the port number, however, and
> clicking it does not retrieve the harvested resource. If the port number is
> inserted into the search result link, retrieval works fine. Even so,
> rewritten links on the retrieved page do not include a port number where
> applicable. So my question is, how do I ensure that port numbers are
> preserved in wayback search results and in rewritten links?
>
> Thanks,
>
> Chris
>