I have a Java webapp creating a pdf and streaming it back to the browser.
byte[] pdf = report.exportPdfToArray(user);
response.setContentType(\"application/pdf
I have tried a solution in java and it worked.
response.setHeader("Content-Disposition","inline; filename=\"MyFile.pdf\"");
response.setContentType("application/pdf; name=\"MyFile.pdf\"");
response.getOutputStream().write(pdfAsBytesArray);
It's weird but it can be useful for someone(maybe someone can tell what is wrong with it):
When I set two headers like:
response.addHeader("content-length", String.valueOf(((FileInputStream) is).getChannel().size()));
response.addHeader("Content-disposition", "attachment; filename=\"MyFileName.doc\"");
It doesn't work. But when I change the order it works as expected:
response.addHeader("Content-disposition", "attachment; filename=\"MyFileName.doc\"");
response.addHeader("content-length", String.valueOf(((FileInputStream) is).getChannel().size()));
MSIE will use the last part of the path info of the request URL (the part after the last /
) as the default filename of the Save As action. It ignores the filename
attribute of the Content-Disposition
header altogether. All other browsers treat that header properly.
You need to change the URL pattern of your PDF servlet to a path mapping. I.e. do not use /pdf
with http://example.com/context/pdf, but rather use /pdf/*
with http://example.com/context/pdf/report.pdf. This way MSIE will use "report.pdf" instead of "pdf" as the default filename for the Save As action.
content-disposition: attachment ....
There is workaround to do so. We can use iframe where iframe will open in html page, iframe will hold the pdf report whereas the html page is independent of iframe. We can edit the title of html page that holds iframe.
<%@ page language="java" contentType="text/html; charset=ISO-8859-1" pageEncoding="ISO-8859-1"%>
<%@taglib prefix="form" uri="http://www.springframework.org/tags/form" %>
<%@taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %>
<html>
<head>
<title>${reportName}</title>
</head>
<body>
<iframe src="/fcWeb/ReportPDFServlet" width="100%" height="100%"></iframe>
</body>
</html>
I can't detect a flaw. Did you check the behavior with other browsers/readers?
As of RFC, it is not defined what the client has to do do with the filename information if displayed inline...