Opening pdf in browser requires a retry

Question

I just updated to the newest version of Reader 10.  On Windows 7 Home - 64 bit, using Internet Explorer 9 - 32 bit, now when I click on a pdf link from within the browser, the pdf does not immediately load.  Instead I see a gray Adobe screen often with the download bar just stalled.  Oddly, if I click on the link in the address bar of the browser (which shows correctly), the pdf file then loads.
I didn't have this problem with the previous version of Reader 10.  Anyone else experiencing this?  Is there a known solution?

Answer 1

Hi, same problem here on an intranet web app.
Grey page, while a retry allow the user to see the file most of time.
I'm collecting datas about IE and windows version impacted.
object tag is writed as :
<OBJECT id=pdfViewer class="pdf" codeType=application/pdf width="100%" height="100%">
<param name="src" value="PagePdfViewer.aspx?p1=20052689&MODE=DocuView&p2=3"/>
</OBJECT>
There are some dom strange behaviours :
some tags are added : <PARAM NAME="_cx" VALUE="43920"><PARAM NAME="_cy" VALUE="24341"> but I can't see them in IE dev tools dom inspector, only in the InnerHtml property of the Object tag.
Additionaly the src param is shown in the dom inspector, but not in the innerHtml proprty...
This work thought on my developer computer, so probably not the cause of the issue.
Server side is (asp.net c#, filename is function parameter) :
FileInfo fi = new FileInfo(fileName);
Response.ClearHeaders();
Response.ClearContent();
Response.ContentType = "application/pdf";
Response.CacheControl = "No-cache";
Response.Cache.SetCacheability(System.Web.HttpCacheability.NoCache);
Response.AddHeader("Content-Length", fi.Length.ToString());
Response.AddHeader("Content-Disposition", "attachment" + "; filename=\"" + fi.Name + "\"");
int chunkSize = 8192;
byte[] buffer = new byte[chunkSize];
int offset = 0;
int read = 0;
using (FileStream fs = File.Open(fileName, FileMode.Open, FileAccess.Read, FileShare.Read))
    while ((read = fs.Read(buffer, offset, chunkSize)) > 0)
        if (!Response.IsClientConnected)
            break;
        Response.OutputStream.Write(buffer, 0, read);
        Response.Flush();
I'm currently unable to reproduce it under development platforms...
compression is not activated on IIS server side (in reference to the workaround for apache described in another thread)
Is there something I can push on server side to workaround the issue ?
Thanks for your support.
Regards,