[
https://issues.apache.org/jira/browse/MNGSITE-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus resolved MNGSITE-546.
-------------------------------------
Resolution: Fixed
> Remove download.cgi
> -------------------
>
> Key: MNGSITE-546
> URL: https://issues.apache.org/jira/browse/MNGSITE-546
> Project: Maven Project Web Site
> Issue Type: Task
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
>
> Any *.cgi link is resolved by
> https://github.com/apache/infrastructure-p6/blob/1bd0e53353181cf46865b5ec8f5e4fa16541ce7e/modules/closer_cgi/files/closer-cgi.conf#L6
> to point to the {{closer.lua}} script.
> There is no longer the need to have local *.cgi resources like
> https://github.com/apache/maven-site/blob/master/content/resources/download.cgi
> which just executes legacy scripts as in the end even
> {{/www/www.apache.org/dyn/mirrors/mirrors.cgi}} will end up with the
> {{closer.lua}} script. Compare with
> https://infra.apache.org/release-download-pages.html#download-page:
> {quote}
> Your Apache project's download page:
> ...
> must have at least one link to the current release. This link must use the
> closer.lua utility. For example:
> https://www.apache.org/dyn/closer.lua/PROJECT/VERSION/SOURCE-RELEASE. (Note:
> the mirrors.cgi and closer.cgi scripts have been deprecated. Calls to them
> redirect to closer.lua.)
> ...
> Assuming you have called your download page download.html, you can invoke our
> global download script by using the URI download.cgi.
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
