Hi All;
I recently modified the report module of our backoffice software
application to serve up a content-disposition: attachment csv on demand
instead of actually creating a tmp file and a link to it (optimization).
It's being served in an ssl environment. The problem is, on our test
server, this process works as advertised (save dialog), but in
production, the disposition is being ignored (all browsers), and the
content is being served inline and dumped to the browser anyway. It's a
pretty standard header arrangement (below). Obviously, there must be
some difference on the server side, but no luck in finding it so far.
Has anyone had a similar issue that can shed some light?
header("Content-type: text/x-csv");
header("Content-Length: ".strlen($csv_raw_output));
header("Content-Disposition: attachment; filename=".$filename);
print $csv_raw_output;
exit;
Thanks!
Randy
_______________________________________________
UPHPU mailing list
[email protected]
http://uphpu.org/mailman/listinfo/uphpu
IRC: #uphpu on irc.freenode.net
