infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-13629) release .sha checksum file download from dist.apache.org is incorrect when using Firefox
Date Tue, 21 Mar 2017 03:54:42 GMT

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

ASF subversion and git services commented on INFRA-13629:
---------------------------------------------------------

Commit 646f3a2c434070b1675a16e2af0a9ca16822ccd1 in infrastructure-puppet's branch refs/heads/deployment
from [~cml]
[ https://git-wip-us.apache.org/repos/asf?p=infrastructure-puppet.git;h=646f3a2 ]

add text/plain mimetype for .sha and .sha2 per INFRA-13629


> release .sha checksum file download from dist.apache.org is incorrect when using Firefox
> ----------------------------------------------------------------------------------------
>
>                 Key: INFRA-13629
>                 URL: https://issues.apache.org/jira/browse/INFRA-13629
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Dists, Subversion
>            Reporter: Robbie Gemmell
>            Assignee: Chris Lambertus
>            Priority: Trivial
>
> We have historically shipped a .sha1 signature file with our releases, but swapped for
a couple of in-progress releases to use .sha file with a SHA512 checksum, as noted in http://www.apache.org/dev/release-distribution.html#sigs-and-sums.
In testing these releases, it was noticed the .sha file failed to download correctly.
> The issue was noticed when the file was grabbed using Firefox, however the file downloads
successfully when using wget or checking out the svn dir of the dist repo. Looking at the
wget output, it is visible that previously the .sha1 mime type was reported as application/x-sha1,
but with the new .sha file it is now being reported as application/x-gzip.
> Forcing a mime type of text/plain in svn with a svn:mime-type propset allows the browser
to view/download the file successfully, but it doesnt feel like this should be needed given
svn itself treats files as text by default and other checksum extensions are handled without
issue.
> https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.18.0-rc1/apache-qpid-proton-j-0.18.0-src.tar.gz.sha
is an example of a file with the issue. Mime type currently not set in svn.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message