infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (INFRA-17067) archive.a.o: incorrect content-type
Date Thu, 27 Sep 2018 22:21:00 GMT


ASF GitHub Bot commented on INFRA-17067:

sebbASF commented on a change in pull request #1178: INFRA-17067

 File path: data/nodes/
 @@ -67,6 +67,7 @@ vhosts_asf::vhosts::vhosts:
       LuaScope thread
       LuaCodeCache stat
       IndexOptions FoldersFirst FancyIndexing
+      AddType text/plain .asc .md5 .sha .sha1 .sha2 .sha256 .sha512 .sha3 .mds
 Review comment:
   Yes, I know.
   But prior to the addition, .asc was working OK, so there must be some other place where
that is defined. Seems to me it would be best to have all the types defined in the same place.

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> archive.a.o: incorrect content-type
> -----------------------------------
>                 Key: INFRA-17067
>                 URL:
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Website
>            Reporter: Sebb
>            Assignee: Chris Lambertus
>            Priority: Minor
>              Labels: pull-request-available
> The Content-Type for the *.sha* extensions is incorrect on archive.a.o.
> It should be text/plain, but it is application/x-gzip.
> Other hash extensions such as md5, sha1 also have the incorrect type.
> $ curl -sqI | grep Content-Type
> Content-Type: text/plain
> $ curl -sqI | grep Content-Type
> Content-Type: application/x-gzip

This message was sent by Atlassian JIRA

View raw message