lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Høydahl (JIRA) <>
Subject [jira] [Commented] (SOLR-10595) Redirect Confluence pages to new HTML Guide
Date Wed, 09 Aug 2017 22:29:00 GMT


Jan Høydahl commented on SOLR-10595:

bq. This already exists - put in and
it redirects to 

This will not survive renames or restructuring. An elegant approach would be that {{/solr/guide/foo}}
would return the page from the *latest* version that returns a 200 response for that page
name. I.e. we could have a CGI that either looks up a static list of valid pages per release
or attempts a HEAD request against newest first and then each older release before returning
a 301 redirect to the correct page.

> Redirect Confluence pages to new HTML Guide
> -------------------------------------------
>                 Key: SOLR-10595
>                 URL:
>             Project: Solr
>          Issue Type: Sub-task
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: documentation
>            Reporter: Cassandra Targett
>            Assignee: Hoss Man
>         Attachments: new-page-urls.txt, page-tree.xml
> Once the new Ref Guide is live, we may want to redirect pages from Confluence to the
new HTML version. 
> I'm undecided if this is the best idea, I can see pros and cons to it. On the pro side,
I think it helps firmly establish the move away from Confluence and helps users adjust to
the new location. But I could see the argument that redirecting is overly invasive or unnecessary
and we should just add a big warning to the page instead.
> At any rate, if we do decide to do it, I found some Javascript we could tell Confluence
to add to the HEAD of each page to auto-redirect. With some probably simple modifications
to it, we could get people to the right page in the HTML site:

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message