[jira] Commented: (INFRA-2177) people.apache.org httpd MIME type bug: .tgz.sha1 => 'Content-Type: application/x-gzip'

["Mark Martinec (JIRA)" <ji...@apache.org>]

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

Mark Martinec commented on INFRA-2177:
--------------------------------------

This is still unresolved. As we are approaching a new release of SpamAssassin, the issue is again hot.


$ HEAD http://people.apache.org/~wtogami/devel/Mail-SpamAssassin-3.3.0-beta1.tar.gz.md5
200 OK
[...]
Content-Type: application/x-gzip

$ HEAD http://people.apache.org/~wtogami/devel/Mail-SpamAssassin-3.3.0-beta1.tar.gz.sha1
200 OK
[...]
Content-Type: application/x-gzip


Files ending in .md5 or .sha1 SHOULD NOT have a Content-Type of application/x-gzip (inherited
from a 'gz' in the middle of their names). I'm not sure what is the most appropriate MIME type
for ascii digest files, but something like text/plain would be just fine (or perhaps text/x-hash or
application/x-signature).

Adding something like the following to the httpd configuration helps:

  AddType text/plain .md5
  AddType text/plain .sha1


> people.apache.org httpd MIME type bug: .tgz.sha1 => 'Content-Type: application/x-gzip'
> --------------------------------------------------------------------------------------
>
>                 Key: INFRA-2177
>                 URL: https://issues.apache.org/jira/browse/INFRA-2177
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Dists
>            Reporter: Justin Mason
>
> hi guys.  from offlist mail about a proposed-release tarball (and accompanying signatures):
> > >> - The files like Mail-SpamAssassin-rules-3.3.0-alpha2.r802600.tgz.md5
> > >> and Mail-SpamAssassin-rules-3.3.0-alpha2.r802600.tgz.sha1 are
> > >> served by [people.apache.org] as 'Content-Type: application/x-gzip',
> > >> and subsequently the web browsers that I tried (opera and lynx)
> > >> both name the resulting file with a .gz appended, which is then
> > >> very wrong - they can't be gunzipped as they are not really
> > >> compressed, and need to be renamed to let 'sa-update --install'
> > >> find them.
> sure enough,
> : 25...; HEAD http://people.apache.org/~jm/devel/Mail-SpamAssassin-rules-3.3.0-alpha2.r802600.tgz.sha1
> 200 OK
> Connection: close
> Date: Mon, 10 Aug 2009 14:33:57 GMT
> Accept-Ranges: bytes
> ETag: "7a5715-5b-470bbe23286c0"
> Server: Apache/2.2.11 (Unix) mod_ssl/2.2.11 OpenSSL/0.9.8e DAV/2
> Content-Length: 91
> Content-Type: application/x-gzip
> Last-Modified: Sun, 09 Aug 2009 21:09:23 GMT
> Client-Date: Mon, 10 Aug 2009 14:34:04 GMT
> Client-Peer: 140.211.11.9:80
> Client-Response-Num: 1
> Could someone check this out?  cheers.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.