[
https://issues.apache.org/jira/browse/LUCENE-8987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17045684#comment-17045684
]
Uwe Schindler commented on LUCENE-8987:
---------------------------------------
I tried to get hold (also together with INFRA) about some redirection issues
but it was not successful. We have to live with that: The way how the
Subversion stuff is included (internal rewrite) causes some strange redirects,
if user is missing the final slash "/" on a directory name:
https://lucene.apache.org/core/8_4_1/analyzers-nori (missing slash at end). The
webserver redirects this to to the "remapped" URL, causing the following URL to
be shown:
https://lucene.apache.org/__root/docs.lucene.apache.org/content/core/8_4_1/analyzers-nori/
(with slash, but also with the "__root/.../") in it.
This only happens with Javadocs and refguide. I only fixed it for the top-level
documentation folders, but with examples like shown before it leads to this
strange looking URL. The reason is the automatic redirect by Apache to the
folder with slash at end.
We should maybe only prevent Googlebot from crawling it, so we don't get those
wrong-looking URLs into the index.
> Move Lucene web site from svn to git
> ------------------------------------
>
> Key: LUCENE-8987
> URL: https://issues.apache.org/jira/browse/LUCENE-8987
> Project: Lucene - Core
> Issue Type: Task
> Components: general/website
> Reporter: Jan Høydahl
> Assignee: Jan Høydahl
> Priority: Major
> Attachments: lucene-site-repo.png
>
>
> INFRA just enabled [a new way of configuring website
> build|https://s.apache.org/asfyaml] from a git branch, [see dev list
> email|https://lists.apache.org/thread.html/b6f7e40bece5e83e27072ecc634a7815980c90240bc0a2ccb417f1fd@%3Cdev.lucene.apache.org%3E].
> It allows for automatic builds of both staging and production site, much
> like the old CMS. We can choose to auto publish the html content of an
> {{output/}} folder, or to have a bot build the site using
> [Pelican|https://github.com/getpelican/pelican] from a {{content/}} folder.
> The goal of this issue is to explore how this can be done for
> [http://lucene.apache.org|http://lucene.apache.org/] by, by creating a new
> git repo {{lucene-site}}, copy over the site from svn, see if it can be
> "Pelicanized" easily and then test staging. Benefits are that more people
> will be able to edit the web site and we can take PRs from the public (with
> GitHub preview of pages).
> Non-goals:
> * Create a new web site or a new graphic design
> * Change from Markdown to Asciidoc
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
