malay.na...@kpn.com wrote:
4.In which browser(s) the problem appears ?
As reported by the application user, response to this question
is, PDF download is working on Firefox and not working on IE.
That is a common problem if the document is requested by HTTPS and
not by HTTP, and if in IE the
Hi Malay,
See inline
On Thu, May 9, 2013 at 4:20 PM, malay.na...@kpn.com wrote:
Hi Martin,
Sorry for the delay response.
Please find the answer your questions.
1.Which version of Wicket was the last one that worked for you ?
*This is the only version we are using (1.5-RC3).*
2.Which
Malay,
Also, what are the HTTP response headers sent in response to the request
to download the PDF?
On Thu, May 9, 2013 at 11:05 AM, Martin Grigorov mgrigo...@apache.orgwrote:
Hi Malay,
See inline
On Thu, May 9, 2013 at 4:20 PM, malay.na...@kpn.com wrote:
Hi Martin,
Sorry for
Hi Martin,
Sorry for the delay response.
Please find the answer your questions.
1.Which version of Wicket was the last one that worked for you ?
This is the only version we are using (1.5-RC3).
2.Which version do you use now ?
1.5-RC3
3.What code do you use to render the PDF?
Hi Malay,
On Wed, May 8, 2013 at 12:14 PM, malay.na...@kpn.com wrote:
Hi Martin,
Any update on this issue?
Please do let us know if you need any information from our side.
I didn't receive a compiled explanation of your problem as I requested.
You just forwarded some long internal
Also, have you tried debugging this on your own? Problems with opening
PDFs in-browser vs. externally are almost always caused by misconfigured
HTTP response headers, specifically Content-Disposition. This happens in
any framework - it's up to you to set the appropriate response headers.
Malay
Hi Martin,
Any update on this issue?
Please do let us know if you need any information from our side.
Thanks Regards,
Malay Kumar Nayak
KPN-ECM-TAM,
IBM India Private Ltd.
EGL C-Block ,2nd Floor
Bangalore
Email:-malan...@in.ibm.com
KPN Account
Mobile-09742290785
