Lee, Insoo wrote:
We never saw this happening until we rolled out our app to the production,
which uses https.
Suggestion: Don't use HTTPS for downloading the PDF.
We see this on FOP FAQ, and the second bullet point says we should not set
any headers
You should not set headers which cause the browser *not* to chache,
please read carefully.
Also, setting only a few standard headers doesn't mean the browser
will always cache the PDF content, most browsers don't do this until
specific headers are set which tell the browser there is an opportunity
to cache. I don't know how to do this, you should ask on a list
specializing in configuring web servers.
Note that even if you set headers which tell the browser the content
can be cached it still isn't oblieged to do so. In particular many IEx
builds (not all) turn off caching for content delivered over HTTPS
completely. If you insist on delivering the PDF over HTTPS, there is
no way to avoid multiple calls for the same URL if the client is IEx.
Either tell your clients to use Mozilla, or complain to MS that they
goofed.
* Cache in the server. Including a parameter in the URL which has a
timestamp as the value may help you to decide whether a request is repeated.
IEx is reported to retrieve a document up to three times, but never more
often. -> what does it mean????/
Detect whether the servlet was called a second (or third) time for the
same URL, and reuse cached content rather then generate the PDF again.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
