Wrong response MIME type for XLS, XLSX and DOCX formats through report execution API

Changed Assigned User from - to @User_306070

---

Same Problem here. Selected format Jasperserver response should bexls application/xls application/vnd.ms-excelxml text/xml application/xmlrtf unknown application/rtfIs there an option to set these types?

Changed Assigned User from @User_306070 to @anonymous

---

maybe related: http://stackoverflow.com/questions/23567429/opening-file-content-resource-excel-of-jasperreports-server-tomcat-with-inte

In our particular case, we tried the next approaches:

 

- we implemented a servlet filter class that tried to detect the wrong MIME type for the response, e.g.: when the response header had the Content-Type header set to "application/xls" we tried to change it to "application/vnd.ms-excel".

This turned out not to work given the response is flushed after being processed by the web service end point.

 

- we checked the MIME types mapped on the conf/web.xml file on the embedded Tomcat and it was properly set. Apparently, setting anyone of this mappings to a dummy MIME type (e.g.: dummy-application/dummy-type) doesn't change anything, JasperReports keeps responding as before, so evidently it doesn't get the MIME types for the response from here.

 

- we implemented a servlet filter class to try to set the Content-Disposition header of the response in the cases when we knew that the MIME type was wrongly set. As we knew that the response was flushed after being processed by the web service end point, we set the header BEFORE being processed as "Content-Disposition: attachment; filename='filename.extension'". This turned out to work, and we were able to download the file with an appropriate file extension.

 

Given that the last solution was like "hacking" the application and not like configuring it, we decided to give a chance to the last release version of JasperReports Server at the time, v5.6.0, and apparently on this release the MIME type of the response was correctly set, so we finally get to a proper solution for our problem. But despite of this, we never could determine what was exactly the cause behind, or even find some documentation about this or how to configure these MIME types.

 

We hope that our experiences on this issue serves to anyone that walks into the same "rock".

Good luck!