cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Piotr Skawinski <>
Subject Re: Different behaviours with MultipartBody (REST) in different browsers
Date Thu, 03 Nov 2011 09:11:54 GMT
Hi Sergey,

Thanks for reply :)

Using multipart/form-data is not solving the problem and firefox now
downloads the file as some default name and not as one specified in
ContentDisposition("**attachment;filename=myfilename.pdf"). The IE is still
only showing the binary content in the browser. I can do some work around
to get it work with IE and to get it show the content of the file in the
browser by doing something like that in the service method declaration:

Response downloadFile(@PathParam("ticket") String ticket,
  @PathParam("fileId") String fileId) throws IOException;

and in the implementation by doing something like that:

return Response.ok(new FileInputStream(file))
  .header("Content-type", "application/pdf")

but then the browsers (all of them) is not offering (in a download popup)
to save the file in the file system.


On Wed, Nov 2, 2011 at 7:11 PM, Sergey Beryozkin <>wrote:

> Hi,
> On 02/11/11 15:04, Piotr Skawinski wrote:
>> Hi,
>> I'm facing different behaviours with MultipartBody on REST services. When
>> using MultipartBody as a return value on a service method annotated with
>> jax-rs annotation like:
>> @GET
>> @Path("/downloadFile/{ticket}/**{fileId}")
>> @Produces("multipart/mixed")
>> MultipartBody downloadFile(@PathParam("**ticket") String
>> ticket, @PathParam("fileId") String fileId) throws IOException;
>> Internet Explorer cannot download the file being included in MultipartBody
>> correctly, but shows only the binary content of MultipartBody (the file
>> being included in it). Chrome and Safari is downloading the content of the
>> file nicely, but is not showing the file name that is specified as:
>> MultipartBody multipartBody = new MultipartBody(new Attachment("eclosure",
>> new FileInputStream(file),
>>  new ContentDisposition("**attachment;filename=" +
>> fileInfo.getFileNameWithCpr())**));
>> Only the Fifefox is downloading the file as expected.
>> Any help will be appriciated.
>>  thanks for this info, if it were possible to somehow compare the
> payloads returned from CXF against some similar payloads from some other
> services then it would probably help, I guess I can try that too but a bit
> later.
> But then Firefox did manage to get it right, so...
> Actually, could it be that other browsers don;t like "multipart/mixed" and
> expect "multipart/form-data" ? Can you try it please ?
> Cheers, Sergey
>  Piotr

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message