There are 2 MS support articles you need to read. Mike's correct in stating IE ignores MIME type - it does a lot of second-guessing. One of the articles deals with that: http://msdn.microsoft.com/library/default.asp?url=/workshop/networking/monik er/overview/appendix_a.asp Another is in the Knowledge Base Q254337 (also Q293792) explaining how astonishingly brain-dead IE can be as it sends 2 or 3 requests ("contype" requests) for every actual request. This can play havoc with server side programs. IMO those should at least be HEAD requests. I believe that constitutes a breach of standards (no news there of course).
Hope this helps at least a little. I assume others on this list already knew about this stuff....? -- Mark Hubbard: [EMAIL PROTECTED] Microsoft Certified Professional "Never apply a Star Trek solution to a Babylon 5 problem." -----Original Message----- From: Mike Hoegeman <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] <[EMAIL PROTECTED]> Date: Wednesday, October 17, 2001 12:58 PM Subject: Re: <embed> tag and ns_returnfile... >i'm not sure this will help but >you might try making the url that generates the pdf file end with >".pdf" (if you not doing that already..) > >i found that some versions of IE don't always pay attention to the content-type >but they will pay attention to the file suffix.. > > >> OK, I have pdflib going in aolserver and it generates beautiful pdf reports. I send them to the browser via 'ns_returnfile 200 application/pdf /tmp/pdffilename'. On some machines it works great. On others, it does not work at all. The root of the problem is something to do with the <embed> tag generated by the browser to display the file. >> >> It seems that the <embed> tag has a URL embedded (no pun intended) in it. I assume the browser sees the header contains a file type that it can embed, so it generates its own <embed> tag and sends it to itself. It then goes back to that url to get the file, taking advantage of the delay the host application (Acrobat) takes to launch to hide this silliness. >> >> If this is true, I can see where I cause it problems, I register a proc to generate a form in which the users specifies criteria for GET requests, and a proc to generate a pdf for POST requests. If the browser is issuing a GET for the url in the <embed> tag, that explains the problem, but not why it works on some machines but not on others. >> >> All browsers are IE5, all Acrobat is 4.0, all clients are Win 98. Of course, there are myriad patchlevels.... >> >> Has anyone else had issues like this with generated pdf where the GET and POST registered procs are similar to mine? >> >> I am thinking the only fix is to return a redirect to a directory where the report is instead of the pdf file itself... >> >> Thanks in advance... >> >> Ian A. Harding >> Programmer/Analyst II >> Tacoma-Pierce County Health Department >> (253) 798-3549 >> mailto: [EMAIL PROTECTED] >> >> > > > >-- > Mike Hoegeman > Email: [EMAIL PROTECTED] > Phone: 805-279-7306
