Hi All,

First of all Wendy, sorry for convincing you to change your Wiki page.
You can change it back if you want to...

Actually I'm totaly confused about this bug I haven't replied earlier
because I
thought that I will set up an apache with ssl here at home so I can find out
what really causes it, but at the moment I don't think that I will spend
time with
this.. after all it's just a stupid bug, it's not that interesting.

So back to the problem:

We have a writePdfToResponse(...) method. This sets the content-type the
content-length and writes the pdf to the response.
This method is called from two Actions one is for GET requests the other is
for POSTs requests.
The same method generates the response for both kind of requests so the
response should be the same in both cases.
For the POST requests I got the "nonsecure items" message box in IE.

On Monday I tried the following things:

1. returned a gif file in the same way --> No "nonsecure items" this time so
it is probably an Acrobat Reader bug.
2. Accessing the page without the open PDF in browser setting. No "nonsecure
items".
3. Wrote a servlet that returns the pdf, mapped it to *.pdf, redirected from
the POST action to the servlet using redirect="true". "nonsecure items"
message box is still there!!! I thougth that this will work because the GET
request doesn't show the "nonsecure items" message box.
4. Used Wendy's approach, sending a html page that hasa meta refresh header.
This worked of course.

But.. the clients didn't like the page an the additional redirect.
So I put back the original code, actually I rewrote it so it is slightly
different and surprise the "nonsecure items" message box is gone!
I checked the older code in subversion and at a first glance it seems I am
doing exactly the same thing. But the message is not there anymore! And I
suddenly lost all my "appetite" to found out the exact circumstances in
which this stupid bug occurs.

So thanks for al your help. Wendy please remove the redirect solution from
your wiki cause it doesn't work! Sorry for that!

Regards,
Tamas

Reply via email to