Re: CFContent and PDF problems
I have had this problem before. My extremely low tech solve was to shutdown browser and then remove adobe from memory through the task manager. hope this helps. ~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;207172674;29440083;f Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:318296 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
RE: CFContent and PDF problems
Two other things to try: 1) As mentioned by Dave Carabetta, try using CFSILENT or CFSETTING ENABLECFOUTPUTONLY="Yes" to restrict extraneous whitespace. For example: TYPE="application/pdf" FILE="C:\Temp\foo.pdf" DELETEFILE="No"> 2) Try appending the desired filename onto the URL. For example: http://www.foo.com/downloadFile.cfm/foo.pdf?fileID=5 -- Mosh Teitelbaum evoch, LLC Tel: (301) 942-5378 Fax: (301) 933-3651 Email: [EMAIL PROTECTED] WWW: http://www.evoch.com/ -Original Message- From: Shawn Grover [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 08, 2003 3:52 PM To: CF-Talk Subject: RE: CFContent and PDF problems Thanks for the reply. I've added "inline;" and "attachement;" to the value of the CFHeader tag - neither one made a difference in the behaviour. I read through the RFC, and this appears to apply more to email than to web pages. However, I made sure I understood the concepts involved. The thing is that we have similar code in production that works fine. In this particular case, our binary files get dumped to the web page as raw text. I can change this behaviour a little to a point where we ARE prompted to save, but then the filename we're prompted with is for the action page, not the one set in the CFHeader tag, and when we do agree to open/save the file, nothing happens (the saving dialog just opens and no data get's transferred). This is repeatable with PDF and DOC files. However, for some reason JPG and GIFs work fine. Thanks again for the reply, but I'm still looking for a solution (digging on my side, as well as hoping someone on the list might be able to help out). Shawn [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
Re: CFContent and PDF problems
Not sure what's wrong with a regular hyperlink to the PDF file if you want to "push files to a client page"? DELETEFILE="no"> ...works for us with PDF's and brings up the "save as" box. Shawn Grover wrote: > > We're using a CFContent to push files to a client page (after they've > clicked on an appropriate link of course). Things are working for image > files, but we are getting odd behaviour when we try to view PDF documents. > > Here's the code in question: > > > > > > > and the supporting variables are: > Mime TYpe: application/pdf > File Name: 2003100809073301noisereport.pdf > Path and File: > C:\inetpub\wwwroot\caa\ctreg_web\fts_files\2003100809073301noisereport.pdf > > What's happening is that the PDF file is getting dumped as raw text to the > page, or we see a prompt to save our action page (getfile.cfm). However, > this is a near exact copy of an existing routine from another application we > did. In the other application, the PDF plug-in kicks in and we view the > file in Adobe Acrobat. It would appear that in the process of copying and > modifying the code, something minor was changed to result in this new > behaviour. However, we've now had 3 people look at the code and we don't > see anyting that should be causing this issue. > > Does anyone see anything wrong or have any suggestions? My thoughts are > that we have missed something stupid... > > Thanks in advance. > > Shawn > > [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
RE: CFContent and PDF problems
Thanks for the reply. I've added "inline;" and "attachement;" to the value of the CFHeader tag - neither one made a difference in the behaviour. I read through the RFC, and this appears to apply more to email than to web pages. However, I made sure I understood the concepts involved. The thing is that we have similar code in production that works fine. In this particular case, our binary files get dumped to the web page as raw text. I can change this behaviour a little to a point where we ARE prompted to save, but then the filename we're prompted with is for the action page, not the one set in the CFHeader tag, and when we do agree to open/save the file, nothing happens (the saving dialog just opens and no data get's transferred). This is repeatable with PDF and DOC files. However, for some reason JPG and GIFs work fine. Thanks again for the reply, but I'm still looking for a solution (digging on my side, as well as hoping someone on the list might be able to help out). Shawn -Original Message- From: Mosh Teitelbaum [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 08, 2003 1:12 PM To: CF-Talk Subject: RE: CFContent and PDF problems Shawn: Your CFHEADER is missing a value. The VALUE for the Content-Disposition header should begin with either "inline;" or "attachment;" as in: VALUE="inline; filename=#oFTS.OriginalName#"> See RFC1806 ( http://www.faqs.org/rfcs/rfc1806.html ) for more details. -- Mosh Teitelbaum evoch, LLC Tel: (301) 942-5378 Fax: (301) 933-3651 Email: [EMAIL PROTECTED] WWW: http://www.evoch.com/ -Original Message- From: Shawn Grover [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 08, 2003 12:52 PM To: CF-Talk Subject: CFContent and PDF problems We're using a CFContent to push files to a client page (after they've clicked on an appropriate link of course). Things are working for image files, but we are getting odd behaviour when we try to view PDF documents. Here's the code in question: and the supporting variables are: Mime TYpe: application/pdf File Name: 2003100809073301noisereport.pdf Path and File: C:\inetpub\wwwroot\caa\ctreg_web\fts_files\2003100809073301noisereport.pdf What's happening is that the PDF file is getting dumped as raw text to the page, or we see a prompt to save our action page (getfile.cfm). However, this is a near exact copy of an existing routine from another application we did. In the other application, the PDF plug-in kicks in and we view the file in Adobe Acrobat. It would appear that in the process of copying and modifying the code, something minor was changed to result in this new behaviour. However, we've now had 3 people look at the code and we don't see anyting that should be causing this issue. Does anyone see anything wrong or have any suggestions? My thoughts are that we have missed something stupid... Thanks in advance. Shawn _ [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
Re: CFContent and PDF problems
>We're using a CFContent to push files to a client page (after they've >clicked on an appropriate link of course). Things are working for image >files, but we are getting odd behaviour when we try to view PDF documents. > >Here's the code in question: > > > >VALUE="filename=#oFTS.OriginalName#"> > > > >and the supporting variables are: > Mime TYpe: application/pdf > File Name: 2003100809073301noisereport.pdf > Path and File: >C:\inetpub\wwwroot\caa\ctreg_web\fts_files\2003100809073301noisereport.pdf > >What's happening is that the PDF file is getting dumped as raw text to the >page, or we see a prompt to save our action page (getfile.cfm). However, >this is a near exact copy of an existing routine from another application >we >did. In the other application, the PDF plug-in kicks in and we view the >file in Adobe Acrobat. It would appear that in the process of copying and >modifying the code, something minor was changed to result in this new >behaviour. However, we've now had 3 people look at the code and we don't >see anyting that should be causing this issue. > >Does anyone see anything wrong or have any suggestions? My thoughts are >that we have missed something stupid... The only issue I've run into is with whitespace. If the binary text of the PDF isn't the absolute very first character on the page, it won't display correctly. Make sure you've cfsilent-ed to absolutely compress all whitespace if you haven't already. Regards, Dave. [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
RE: CFContent and PDF problems
Shawn: Your CFHEADER is missing a value. The VALUE for the Content-Disposition header should begin with either "inline;" or "attachment;" as in: VALUE="inline; filename=#oFTS.OriginalName#"> See RFC1806 ( http://www.faqs.org/rfcs/rfc1806.html ) for more details. -- Mosh Teitelbaum evoch, LLC Tel: (301) 942-5378 Fax: (301) 933-3651 Email: [EMAIL PROTECTED] WWW: http://www.evoch.com/ -Original Message- From: Shawn Grover [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 08, 2003 12:52 PM To: CF-Talk Subject: CFContent and PDF problems We're using a CFContent to push files to a client page (after they've clicked on an appropriate link of course). Things are working for image files, but we are getting odd behaviour when we try to view PDF documents. Here's the code in question: and the supporting variables are: Mime TYpe: application/pdf File Name: 2003100809073301noisereport.pdf Path and File: C:\inetpub\wwwroot\caa\ctreg_web\fts_files\2003100809073301noisereport.pdf What's happening is that the PDF file is getting dumped as raw text to the page, or we see a prompt to save our action page (getfile.cfm). However, this is a near exact copy of an existing routine from another application we did. In the other application, the PDF plug-in kicks in and we view the file in Adobe Acrobat. It would appear that in the process of copying and modifying the code, something minor was changed to result in this new behaviour. However, we've now had 3 people look at the code and we don't see anyting that should be causing this issue. Does anyone see anything wrong or have any suggestions? My thoughts are that we have missed something stupid... Thanks in advance. Shawn [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
CFContent and PDF problems
We're using a CFContent to push files to a client page (after they've clicked on an appropriate link of course). Things are working for image files, but we are getting odd behaviour when we try to view PDF documents. Here's the code in question: and the supporting variables are: Mime TYpe: application/pdf File Name: 2003100809073301noisereport.pdf Path and File: C:\inetpub\wwwroot\caa\ctreg_web\fts_files\2003100809073301noisereport.pdf What's happening is that the PDF file is getting dumped as raw text to the page, or we see a prompt to save our action page (getfile.cfm). However, this is a near exact copy of an existing routine from another application we did. In the other application, the PDF plug-in kicks in and we view the file in Adobe Acrobat. It would appear that in the process of copying and modifying the code, something minor was changed to result in this new behaviour. However, we've now had 3 people look at the code and we don't see anyting that should be causing this issue. Does anyone see anything wrong or have any suggestions? My thoughts are that we have missed something stupid... Thanks in advance. Shawn [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
