Re: Downloading generated PDF behavior different with apache in front of appserver

[TahitianGabriel]

Are you using IE?

There are many troubles generating PDF over SSL.

See for an example :
http://eirikhoem.wordpress.com/2007/06/15/generated-pdfs-over-https-with-internet-explorer/
http://eirikhoem.wordpress.com/2007/06/15/generated-pdfs-over-https-with-internet-explorer/
 


If you google IE PDF SSL, you will find many answers.

Here's the workaround I use in my wicket applications (i'm generating PDF
with jasperreports) :
WebResponse response = (WebResponse)
getRequestCycle().getResponse();
response.setDateHeader(Expires, -1);
response.setHeader(Pragma, public);
response.setHeader(Cache-Control, public);

Regards,

Gabriel.
-- 
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Downloading-generated-PDF-behavior-different-with-apache-in-front-of-appserver-tp2336943p2338770.html
Sent from the Wicket - User mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Downloading generated PDF behavior different with apache in front of appserver

[Doug Leeper]

All,

We have an application that generates a PDF (via PD4ML) and sends it back in 
the 
same request.  This works fine and dandy when accessing our app server 
(weblogic/http) directly.  However, when we access the same functionality but 
via Apache and SSL to weblogic, we get a message that the resultant file is 
corrupted.  Not sure why this is occurring.   It appears that stream is being 
closed before the content upload has been completed.  We have static PDF served 
up via apache/weblogic that don't have any problems.

Does anyone have any idea where I need to start looking?  I am assuming this is 
not a Wicket issue as it works when the appserver is accessed directly but 
could 
be wrong.

Thanks
- Doug