Jonathan Linczak wrote:
> Yup, that's what I was referring to. I actually made the change to
> our server and it doesn't seem to make a difference. But while I'd
> like to test with Tomcat, there's no way I'm switching back after the
> good luck I've been having with Jetty. :) Here's another document
> that has some discussion on the issue, but no real concrete answers
> for me, unless you see something useful:
>
http://72.14.207.104/search?q=cache:JUZXj0O4yXAJ:www.newsarch.com/
> archive/mailinglist/comp/java/jetty/general/
> msg00360.html+Jetty+IE+%22The+file+is+damaged+and+could+not+be+repaired.
> %22&hl=en&client=firefox-a. I'll see if the test instance of Tomcat
> serving the same PDF document solves the issue and post a response
> here.
"If the request for the PDF document is being handled by MSIE it appears
to start downloading the content, then decides that it really should
have invoked the PDF plug-in. It then just 'pulls the plug' on that
request-response pair and passes control to the plug-in, which has to
start again. This may explain some of the broken connections."
i had this problem in a customer project, and when i debugged it with
http headers, ie would request pdf differently than ff. in my case, i
was able to so solve the problems by playing with the expiry / cache
headers that get sent along (in the sitemap). sorry i do not recall all
the details, maybe it was this:
http://www.planetpdf.com/forumarchive/55559.asp---------------------------------------------------------------------
To unsubscribe, e-mail:
user-unsubscribe@...
For additional commands, e-mail:
user-help@...