> I have a problem with the artifacts. I configured artifacts with label
> PAR and copy pattern */.par. This is a special zip format. If I
> download the file with ending par, the browser opens the file in a text
> editor. The download should use the client information about the file
> type, or?
The content type is set to text/html when downloading the par file, this is very inconvenient on IE.
- mentioned in
-
Page Loading...
[BAM-1635] Artifacts with ".par" extensions get downloaded as text files
Adrian Hempel [Atlassian]
added a comment - Although the text/html MIME type may have been intended to force artifacts with unrecognised file extensions to display in the browser, a consequence of another recent change, targeted for Bamboo 1.2.3, is that all artifacts are downloaded, rather than displayed in the browser.
The behaviour of Internet Explorer is to produce a file download dialog, which is what the customer is wanting.
Adrian Hempel [Atlassian]
added a comment - Although the text/html MIME type may have been intended to force artifacts with unrecognised file extensions to display in the browser, a consequence of another recent change , targeted for Bamboo 1.2.3, is that all artifacts are downloaded, rather than displayed in the browser.
The behaviour of Internet Explorer is to produce a file download dialog, which is what the customer is wanting. Looking at the code, the default MIME type for unrecognised file extensions is text/html. It might be more appropriate to default to application/octet-stream.
I'm considering it.
Adrian Hempel [Atlassian]
added a comment - - edited Looking at the code , the default MIME type for unrecognised file extensions is text/html . It might be more appropriate to default to application/octet-stream .
I'm considering it. Adrian Hempel [Atlassian]
added a comment - It would be unwise to map the "par" file extension to "application/zip", as this would does not appear to be the most common use of the "par" file extension.
I suggest that the customer add the following section to the WEB-INF/mimetypes.xml file in their Bamboo installation:
<mime-mapping> <extension>par</extension> <mime-type>application/zip</mime-type> </mime-mapping>
Adrian Hempel [Atlassian]
added a comment - It would be unwise to map the "par" file extension to "application/zip", as this would does not appear to be the most common use of the "par" file extension .
I suggest that the customer add the following section to the WEB-INF/mimetypes.xml file in their Bamboo installation:
<mime-mapping>
<extension> par </extension>
<mime-type> application/zip </mime-type>
</mime-mapping>
I've given Ajay the information the customer needs to make the necessary configuration change.
As a consequence of
BAM-402, Bamboo 1.2.3 will behave in the way that the customer requires (but this may not be other customers require, so I've raisedBAM-1642, which will provide a choice).