On Sep 1, 2005, at 3:45 AM, J. Wolfgang Kaltz wrote:
Linczak, Jonathan W. schrieb:
(...)
Then I go to Lenya, click on the link in IE/Win with Acrobat 7
combination and the file is working. Thank God, I think to myself.
I finally solved the problem. So then I check out the live
environment - same computer, same setup. "The file is corrupt or
damaged and cannot be repaired." So what the heck? It doesn't make
any sense - it seems to be completely random. I'm serving the same
file on the same computer and same setup with the only difference is
one is in the authoring environment and the other is in the live
environment and the results are different. Then some files now work
in the live environment and others do not.
Just as an example, go ahead and check out this page:
http://alumni.hiram.edu/events/homecoming.html. Click on the big link
using IE/Win with Acrobat Reader as plugin and see what you get. I
continue to get file damaged errors, but some people say they can see
it fine. It just seems so random. Anyone have any ideas? I'm
feeling pretty helpless on this one...
Jon, we had the same problem a couple of years ago, unfortunately I
can't find the solution from that time. It was Apache-based anyway,
and involved telling Apache to do a workaround in the http headers for
this IE+Adobe problem. I can't remember if the workaround involved
changing the expires header or not; whatever the workaround was, it no
longer seems necessary (we did a new system installation a few months
ago) and google can not find the pages I found on that subject back
then :/
So I'm sorry I can't really help you, but what I would suggest you do:
- the apparent "randomness" in Web stuff usually comes from caching
problems. Whatever you may have set in the server, I suggest that
before any client test, you clear the browser's cache
- regarding differences in environments, be sure to know the whole
chain of software in both situations. Unfortunately, any piece of
software might change your http headers on the way; that includes
things like proxies and sometimes firewalls, too.
I found this interesting thread that looked at using mod_proxy as being
the problem by not sending the content-length header. Here's the link:
http://www.issociate.de/board/post/4366/
pdf_with_byterange_doesn't_work,_or_why_content-
length_is_removed_by_mod_proxy.html
I did this as a test through mod_proxy and without and sure enough the
content-length is removed. Of course, the blame is on the IE browser
and their solution is to have IE forced to use HTTP/1.0. And of
course, that was 2 years ago - although I realize that IE hasn't
changed much in quite a long time. I added the following item into my
virtualhost configuration in Apache:
BrowserMatch "MSIE 6\.0;" nokeepalive downgrade-1.0 force-response-1.0
A quick test of this reveals that it does absolutely nothing to help
the situation. If the bug is display the content-length header, is
there a way to force this? Am I even going in the right direction of
finding out the problem? I know we're kinda trailing off the whole
Lenya thing, but if this is a common setup for people, surely others
are going to experience this, and it only happened after I moved to
Jetty built in to Lenya. If you guys were going to check this out,
what would be the first things you would do to figure out this problem?
Jon
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
