[Deploying Sakai] [Building Sakai] content.mime.inline and Sakai 2.7.1 or later

Jean-Francois Leveque jean-francois.leveque at upmc.fr
Fri Jan 6 02:18:16 PST 2012

Hi Earle,

I get this with help from Live HTTP Headers:
> Content-Disposition: attachment; filename="krystalshaper.jar"

Thank you for helping confirm the forced download.

Any idea how I can fix this?


On 05/01/2012 23:23, Earle Nietzel wrote:
> Hi JF,
> Can you check the headers you are getting when downloading the jar file.
> If you see anything with a header of "content-disposition" value
> "attachment;" you are not getting the inline version but being forced to
> download.
> Earle
> On Thu, Jan 5, 2012 at 11:33 AM, Jean-Francois Leveque
> <jean-francois.leveque at upmc.fr <mailto:jean-francois.leveque at upmc.fr>>
> wrote:
>     Hi,
>     The content.mime.inline configuration property was added in Sakai 2.6.
>     content.html.forcedownload configuration was added in Sakai
>     2.6.3/2.7.0. <http://2.7.0.>
>     I have a user who uploads applets (html+jar) in resources.
>     He's found out today they are not working anymore since we left 2.7.0 a
>     long time ago.
>     It looks like the jar file download is forced and this might be why is
>     applet isn't working anymore. Creating a content.mime.inline list with
>     the mime type of the jar (application/x-zip-compressed as seen in the
>     jar file details) doesn't work with my 2.8.
>     Changing the file details as a temporary workaround doesn't seem to work
>     either.
>     Any ideas?
>     Cheers,
>     J-F

More information about the production mailing list