Sebb created MNGSITE-260:
----------------------------
Summary: Download pages don't use customised versions
Key: MNGSITE-260
URL: https://issues.apache.org/jira/browse/MNGSITE-260
Project: Maven Project Web Site
Issue Type: Bug
Reporter: Sebb
The download pages for maven plugins are being redirected to the default ASF
download page, rather than using the specific pages.
For example:
http://maven.apache.org/plugins/maven-clean-plugin/
has the download link
http://maven.apache.org/plugins/maven-clean-plugin/download.html
which is redirected by the Maven .htaccess file to
http://maven.apache.org/plugins/maven-clean-plugin/download.cgi
which uses the default ASF download page.
This is because all .cgi script accesses are now rewritten to use closer.lua.
The closer.lua script uses the original cgi url details to find the correct
HTML skeleton page; if it cannot find the page, then it defaults to the basic
ASF page at
http://www.apache.org/dyn/closer.html
It cannot find the correct html file because it is not at the original
location; there are other redirects in the Maven htaccess file [1] which mean
the html file is actually to be found at:
http://maven.apache.org/components/plugins/maven-clean-plugin/download.html
The closer.lua script needs to know the correct location of the html file after
any redirects.
So a work-round is to change the download link from
http://maven.apache.org/plugins/maven-clean-plugin/download.html
to
http://maven.apache.org/components/plugins/maven-clean-plugin/download.html
However, I think the problem is probably due to the following unconditional
redirect:
RedirectMatch permanent ^/(.*)/download.html$
http://maven.apache.org/$1/download.cgi
which appears at the start of the file.
If this were done at the end of the file, it might allow the server to pass the
actual html file location to the closer.lua script.
Worth a try.
[1]
https://svn-master.apache.org/repos/infra/websites/production/maven/content/.htaccess
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
