Re: IE Content Disposition Problem

No it's not, I explicity wanted it to download.

> >Changing the content type was not needed. Cheers !
>
> Well, I'm just glad to help.
> Actually, setting the content-type correctly, will help browsers to
> automatically open documents in their native applications or the
> alternative
> open the file inside the browser itself. But, of course, this might not be
> the effect you desire.
>
>
> Mvh
> Thor
>
> -----Original Message-----
> From: owner-resin-interest@xxx.com
> [mailto:owner-resin-interest@xxx.com] On Behalf Of sks - global7
> Sent: 18. oktober 2005 21:26
> To: resin-interest@xxx.com
> Subject: Re: IE Content Disposition Problem
>
> Adding in the cache-control header has solved the problem. Changing the
> content type was not needed. Cheers !
>
>> Hi,
>>
>> I'm doing exactly that, but with different filetypes, so my code looks
>> like
>> this:
>>
>> response.setContentType(theCurrentMIMEType);
>> response.setHeader("Content-Disposition","attachment;
>> filename=\""+theCurrentFileName+"\"");
>> response.setHeader("Cache-Control", "private");
>>
>> And that works, I believe there could be some strange issues in IE
>> when NOT setting the correct MIME and the Cache-Control.
>> Let me know if it works.
>>
>>
>> Mvh
>> Thor
>>
>> -----Original Message-----
>> From: owner-resin-interest@xxx.com
>> [mailto:owner-resin-interest@xxx.com] On Behalf Of sks - global7
>> Sent: 18. oktober 2005 11:56
>> To: resin-interest@xxx.com
>> Subject: IE Content Disposition Problem
>>
>> Morning people,
>>
>>
>> I am getting the exact same error this guy was:
>> http://www.caucho.com/support/resin-interest/0007/0083.html
>>
>> No one ever replied with a solution though as it went off on a tangent
>> about
>> content lengths.
>>
>> I'm using this:
>>
>> response.setContentType("application/octet-stream");
>> response.setHeader("Content-Disposition", "attachment; filename=\"" +
>> result.getFilename() + "\"");
>>
>> Tried all variations on the latter (no quotes, semi colon terminator,
>> etc).
>> Works perfectly in Firefox.
>>
>>
>>
>
>
>
Received on Wed 19 Oct 2005 01:46:00 -0700