forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Crossley (JIRA)" <>
Subject [jira] Commented: (FOR-677) leading slash in gathered URIs causes double the number of links to be processed
Date Wed, 21 Sep 2005 00:31:27 GMT
    [ ] 

David Crossley commented on FOR-677:

We have stylesheets in main/webapp/resources that do that "relativise" and "absolutise" job.
These are called from main/webapp/linkmap.xmap:74 and elsewhere. The main thing is that for
each page that is processed, its linkmap is made relative, so we could trim the leading slash
there, i.e. this is all internal to Forrest. Asking because concerned about side-effects.

> leading slash in gathered URIs causes double the number of links to be processed
> --------------------------------------------------------------------------------
>          Key: FOR-677
>          URL:
>      Project: Forrest
>         Type: Bug
>   Components: Core operations
>     Versions: 0.8-dev, 0.7
>     Reporter: David Crossley
>      Fix For: 0.8-dev

> Doing 'forrest' starts at the virtual document called linkmap.html where the Cocoon crawler
gathers the initial set of links, then starts crawling and generating pages. Any new links
are pushed onto the linkmap. However, for some sites, such as our own "seed-sample" and our
"site-author", there is a sudden jump in the number of URIs remaining to be processed.
> This is due to a URI with a leading slash (e.g. /samples/faq.html). When that URI is
processed, it gains a whole new set of links all with leading slashes, and so the list of
URIs is potentially doubled.
> This issue could be due to a user error, i.e. adding a link that deliberately begins
with a slash. Sometimes, that is unavoidable.
> However, we do have a sitemap transformer to "relativize" and "absolutize" the links.
Should it always trim the leading slash? Or are there cases where that should not happen,
so cannot generalise?

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message