infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robbie Gemmell (JIRA)" <>
Subject [jira] [Commented] (INFRA-13629) release .sha checksum file download from is incorrect when using Firefox
Date Thu, 09 Mar 2017 11:54:37 GMT


Robbie Gemmell commented on INFRA-13629:

Setting the mime type in the svn repo to "application/x-sha" or "application/x-sha2" also
lets things work, with the same then being reported when downloaded from the webserver with
wget, and the file being downloaded ok in Firefox and indicated as ".sha file" type in Firefox.
I tried those since the webserver is automatically using "application/x-sha1" on .sha1 files,
and "application/x-md5" on .md5 files (which dont have a mime-type set in svn).

Can we figure out where the webserver bits are doing this mime type selection and update them
to report something other than "application/x-gzip"?

> release .sha checksum file download from is incorrect when using Firefox
> ----------------------------------------------------------------------------------------
>                 Key: INFRA-13629
>                 URL:
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Dists, Subversion
>            Reporter: Robbie Gemmell
> 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
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
is an example of a file with the issue. Mime type currently not set in svn.

This message was sent by Atlassian JIRA

View raw message