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

[Earle Nietzel]

Hi JF,

After doing some testing I added the

content.mime.inline.count=1
content.mime.inline.1=**application/x-java-archive

I uploaded a jar file to resources verified the mime type and then chose to
download it was streamed with
Content-Disposition: inline

So I was able to get it to work right.

Earle

On Mon, Jan 9, 2012 at 8:37 AM, Jean-Francois Leveque <
jean-francois.leveque at upmc.fr> wrote:

> Hi Earle,
>
> UI
> Type du fichier         application/x-java-archive
>
> HTTP
> Content-Type: application/x-java-archive
>
> sakai.properties
> content.mime.inline.count=1
> content.mime.inline.1=**application/x-java-archive
>
> Still forced to download. :(
>
> Source code for content i 2.8.0 + SAK-14625 with kernel 1.2.5.
>
> Anything else I should mention or check?
>
> J-F
>
>
> On 06/01/2012 20:43, Earle Nietzel wrote:
>
>> Ok so what you want to achieve is a disposition like:
>>
>> Content-Disposition: inline; filename="krystalshaper.jar"
>>
>> Can you check that resource's mime type in sakai and make sure it is the
>> same that you have in "content.mime.inline"?
>>
>> You can check this using "Edit Details" then toward the bottom you will
>> see "File Type".
>>
>> Earle
>>
>>
>>
>>
>> On Fri, Jan 6, 2012 at 5:18 AM, Jean-Francois Leveque
>> <jean-francois.leveque at upmc.fr <mailto:jean-francois.leveque@**upmc.fr<jean-francois.leveque at upmc.fr>
>> >>
>>
>> wrote:
>>
>>    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?
>>
>>    J-F
>>
>>
>>    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@**upmc.fr<jean-francois.leveque at upmc.fr>
>> >
>>        <mailto:jean-francois.leveque@ upmc.fr
>>
>>        <mailto:jean-francois.leveque@**upmc.fr<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.> <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
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20120110/78cd8b5f/attachment.html