I think I have your solution! It's been a long time but I know this worked for me when I used Webshare so I started up my old server and served a PDF file without any problem.
I then looked at my HTTPD CONFIG file and noticed that my config file had 'binary' listed for file type of PDF and mime type of application/pdf. Here is my line: type pdf 0 application/pdf binary When I changed it to 8bit, I got the same error message you are getting. So, it should be set to binary. Hope this helps. Aria On Fri, 10 Apr 2009 17:13:00 -0400 Alan Altmark said: >On Friday, 04/10/2009 at 04:45 EDT, "Schuh, Richard" <[email protected]> >wrote: >> I disabled the plug-in and got the same result. > >If you can get the PDF file to another web server where it DOES work, it >would be interesting to know what the HTTP headers look like. > >It could be that the 'engine' in Acrobat is expecting to have received a >chunk of data all at once and the chunk is spread across TCP segments, >frustrating the code. A change to the buffer allocations in profile tcpip >might give different results. It's reaching, I know, but I used up all my >horses. Zebras are all I have. > >Alan Altmark >z/VM Development >IBM Endicott >
