According to that post, the Acrobat Reader is to blame for
that. It ignores all relevant headers. I do not see a way
to fix that for now, other than "faking" a file on the server
via some HTTP-redirect magic and loads of filters.
If it is important enough to potentially break existing
(1) On a "renderType=REPORT" request we return immediately
with a HTTP-302 response forwarding the browser to
(2) The reporting plugin then checks for a "extra-path" that
starts with "/render/" and proceeds with the normal report
generation and sends the content.
(1) Creating a report requires at least one extra call to the server
for the 302-response and the next GET
(2) It may break OEMs who are not prepared to handle 302 responses
or who use these responses as "Authentication failure". We use that
sort of trick for the publish code, so I assume it is used elsewhere as well.
(3) Generating a PDF from XAction or Analzyer probably
suffers from the same problem, so expect to do more fixing there as
(4) I do not know how the dashboards or other integration points will react
to a 302 response. They may or may not work properly.