[ 
https://issues.apache.org/jira/browse/DERBY-7093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17240335#comment-17240335
 ] 

Richard N. Hillegas commented on DERBY-7093:
--------------------------------------------

According to Daniel Gruno (see INFRA-21149), only one dot is now allowed in the 
names of download pages and cgi scripts. This was a security enhancement which 
INFRA made recently.

So I believe that the fix is to do the following:

* Rename the 10.15.2.0 and 10.14.2.0 html pages and cgi scripts to 
release-10_15_2_0.html, release-10_15_2_0.cgi, release-10_14_2_0.html, and 
release-10_14_2_0.cgi.
* Update the links to them on the master download page at 
http://db.apache.org/derby/derby_downloads.html
* Update the release publication instructions cited by Bryan.
* Update the release generation and publication targets so that, going forward, 
underscores (rather than dots) separate version number components in the names 
of release pages.

> Download Link for 10.15.2.0 is broken
> -------------------------------------
>
>                 Key: DERBY-7093
>                 URL: https://issues.apache.org/jira/browse/DERBY-7093
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 10.15.2.0
>            Reporter: Kevin Young
>            Priority: Minor
>
> The link to download 10.15.2.0 from this page 
> [https://db.apache.org/derby/derby_downloads.html 
> |https://db.apache.org/derby/derby_downloads.html]  incorrectly brings the 
> user to 
> [https://db.apache.org/derby/releases/release-10.15.2.0.{color:#FF0000}cgi{color}]{color:#FF0000}
>   i{color}nstead of 
> [https://db.apache.org/derby/releases/release-10.15.2.0.html] additionally 
> when the user forces the page to the html site, the download links for the 
> binaries bring the user to this broken link 
> https://db.apache.org/derby/releases/{color:#FF0000}[preferred]{color}/db/derby/db-derby-10.15.2.0/db-derby-10.15.2.0-bin.zip
>  
> if someone points me to where this is all set, i could attempt to fix it.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to