Hi, I created a new document in my CMF personal folder, and uploaded a PDF file. The MIME type switches to application/pdf. Till now, all's OK. But when I try to open that document later from the CMF (Whatever browser), I'm asked 3 (!) times for a local destination file and the PDF does not open in the Acrobat Reader plugin of the browser as usual (when creating an usual Zope "file" object then upload a PDF file, all's fine). Is it a CMF bug or did I miss something ? --Gilles
Try Netscape, is there the same problem? If not, you can try this: The error occurs because by the installation of Acrobat Reader 3.xx oder 4.xx one File is not in the MS-Internet Explorer Folder copied. Workaround: - the hidden File nppdf32.dll C:\Program Files\Adobe\Acrobat x.xx\Reader\browser\ has to be copied into C:\Program Files\Internet Explorer\Plugins. (x.xx stands for the version) Hope it helps br stefan -----Ursprüngliche Nachricht----- Von: zope-admin@zope.org [mailto:zope-admin@zope.org] Im Auftrag von Gilles Lenfant Gesendet: Dienstag, 19. Juni 2001 12:51 An: zope@zope.org Betreff: [Zope] PDF documents in CMF (1.0) Hi, I created a new document in my CMF personal folder, and uploaded a PDF file. The MIME type switches to application/pdf. Till now, all's OK. But when I try to open that document later from the CMF (Whatever browser), I'm asked 3 (!) times for a local destination file and the PDF does not open in the Acrobat Reader plugin of the browser as usual (when creating an usual Zope "file" object then upload a PDF file, all's fine). Is it a CMF bug or did I miss something ? --Gilles _______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Thanks Stephan but... The probleme is on server side as I mentioned in the original post. When I create a Zope "File" object and upload a PDF file, it always works: means that with IE/Netscape/Acrobat reader/Windows/Mac, either the PDF file is opened in the Browser window (through the Acrobat plugin) or it creates an Acrobat window that shows the document. The problem is in the CMF 1.0 (bug or what ?) ----- Original Message ----- From: "Stefan Winandy" <stefan.winandy@topmail.de> To: <zope@zope.org> Sent: Tuesday, June 19, 2001 2:17 PM Subject: AW: [Zope] PDF documents in CMF (1.0) Try Netscape, is there the same problem? If not, you can try this: The error occurs because by the installation of Acrobat Reader 3.xx oder 4.xx one File is not in the MS-Internet Explorer Folder copied. Workaround: - the hidden File nppdf32.dll C:\Program Files\Adobe\Acrobat x.xx\Reader\browser\ has to be copied into C:\Program Files\Internet Explorer\Plugins. (x.xx stands for the version) Hope it helps br stefan
I haven't found the root problem, but I discovered that if the object name ends in .pdf everything works as desired. I traced the headers generated by CMF and the MIME type is set correctly, but the browser seems to want to see the .pdf extension. CMF gives the download the same name as the object id (not the original client-side file-name), so changing the object name to something.pdf seems to satisfy the browser. I agree, this shouldn't be necessary. I'm copying this email to the CMF list, in hopes someone there knows more about the issue. -- Loren
-----Original Message----- From: zope-admin@zope.org [mailto:zope-admin@zope.org]On Behalf Of Gilles Lenfant Sent: Tuesday, June 19, 2001 03:51 To: zope@zope.org Subject: [Zope] PDF documents in CMF (1.0)
Hi,
I created a new document in my CMF personal folder, and uploaded a PDF file. The MIME type switches to application/pdf. Till now, all's OK. But when I try to open that document later from the CMF (Whatever browser), I'm asked 3 (!) times for a local destination file and the PDF does not open in the Acrobat Reader plugin of the browser as usual (when creating an usual Zope "file" object then upload a PDF file, all's fine).
Is it a CMF bug or did I miss something ?
--Gilles
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Loren, Whatever the ID (xxx.pdf or xxx.yyy) of the object the problem remains! --Gilles ----- Original Message ----- From: "Loren Stafford" <lstafford@morphics.com> To: <zope@zope.org>; "Gilles Lenfant" <glenfant@bigfoot.com> Cc: "Zope-Cmf" <zope-CMF@zope.org> Sent: Tuesday, June 19, 2001 5:53 PM Subject: RE: [Zope] PDF documents in CMF (1.0)
I haven't found the root problem, but I discovered that if the object name ends in .pdf everything works as desired. I traced the headers generated by CMF and the MIME type is set correctly, but the browser seems to want to see the .pdf extension. CMF gives the download the same name as the object id (not the original client-side file-name), so changing the object name to something.pdf seems to satisfy the browser.
I agree, this shouldn't be necessary. I'm copying this email to the CMF list, in hopes someone there knows more about the issue.
-- Loren
-----Original Message----- From: zope-admin@zope.org [mailto:zope-admin@zope.org]On Behalf Of Gilles Lenfant Sent: Tuesday, June 19, 2001 03:51 To: zope@zope.org Subject: [Zope] PDF documents in CMF (1.0)
Hi,
I created a new document in my CMF personal folder, and uploaded a PDF file. The MIME type switches to application/pdf. Till now, all's OK. But when I try to open that document later from the CMF (Whatever browser), I'm asked 3 (!) times for a local destination file and the PDF does not open in the Acrobat Reader plugin of the browser as usual (when creating an usual Zope "file" object then upload a PDF file, all's fine).
Is it a CMF bug or did I miss something ?
--Gilles
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Then perhaps you have encountered a different problem than I. Have you tried using tcpwatch.py to ensure that the headers are generated correctly? http://www.zope.org/Members/hathawsh/tcpwatch -- Loren
-----Original Message----- From: zope-admin@zope.org [mailto:zope-admin@zope.org]On Behalf Of Gilles Lenfant Sent: Tuesday, June 19, 2001 11:13 To: zope@zope.org Subject: Re: [Zope] PDF documents in CMF (1.0)
Loren,
Whatever the ID (xxx.pdf or xxx.yyy) of the object the problem remains!
--Gilles
----- Original Message ----- From: "Loren Stafford" <lstafford@morphics.com> To: <zope@zope.org>; "Gilles Lenfant" <glenfant@bigfoot.com> Cc: "Zope-Cmf" <zope-CMF@zope.org> Sent: Tuesday, June 19, 2001 5:53 PM Subject: RE: [Zope] PDF documents in CMF (1.0)
I haven't found the root problem, but I discovered that if the object name ends in .pdf everything works as desired. I traced the headers generated by CMF and the MIME type is set correctly, but the browser seems to want to see the .pdf extension. CMF gives the download the same name as the object id (not the original client-side file-name), so changing the object name to something.pdf seems to satisfy the browser.
I agree, this shouldn't be necessary. I'm copying this email to the CMF list, in hopes someone there knows more about the issue.
-- Loren
-----Original Message----- From: zope-admin@zope.org [mailto:zope-admin@zope.org]On Behalf Of Gilles Lenfant Sent: Tuesday, June 19, 2001 03:51 To: zope@zope.org Subject: [Zope] PDF documents in CMF (1.0)
Hi,
I created a new document in my CMF personal folder, and uploaded a PDF file. The MIME type switches to application/pdf. Till now, all's OK. But when I try to open that document later from the CMF (Whatever browser), I'm asked 3 (!) times for a local destination file and the PDF does not open in the Acrobat Reader plugin of the browser as usual (when creating an usual Zope "file" object then upload a PDF file, all's fine).
Is it a CMF bug or did I miss something ?
--Gilles
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Loren Stafford writes:
I haven't found the root problem, but I discovered that if the object name ends in .pdf everything works as desired. I traced the headers generated by CMF and the MIME type is set correctly, but the browser seems to want to see the .pdf extension. CMF gives the download the same name as the object id (not the original client-side file-name), so changing the object name to something.pdf seems to satisfy the browser. I have seen this with IE. Apparently, it does not trust the "Content-Type" but wants to have a corresponding name suffix, too.
Dieter
Dieter Maurer wrote:
Loren Stafford writes:
I haven't found the root problem, but I discovered that if the object name ends in .pdf everything works as desired. I traced the headers generated by CMF and the MIME type is set correctly, but the browser seems to want to see the .pdf extension. CMF gives the download the same name as the object id (not the original client-side file-name), so changing the object name to something.pdf seems to satisfy the browser. I have seen this with IE. Apparently, it does not trust the "Content-Type" but wants to have a corresponding name suffix, too.
CMF 1.0 had a 'download' method for File objects which tried to do the Right Thing (TM) by setting the 'Content-Disposition' header; unfortunately, the browsers didn't support it. That method is deprecated, and no longer surfaced, in CMF 1.1; instead, when the File object is published directly (the URL points to it, with no method appended), we initiate the download; the browsers all do the correct thing in that case. Tres. -- =============================================================== Tres Seaver tseaver@digicool.com Digital Creations "Zope Dealers" http://www.zope.org
participants (5)
-
Dieter Maurer -
Gilles Lenfant -
Loren Stafford -
Stefan Winandy -
Tres Seaver