1) As mentioned by Dave Carabetta, try using CFSILENT or CFSETTING
ENABLECFOUTPUTONLY="Yes" to restrict extraneous whitespace. For
example:
<CFSETTING ENABLECFOUTPUTONLY="Yes">
<CFHEADER NAME="content-disposition" VALUE="inline; filename=foo.pdf">
<CFCONTENT
TYPE="application/pdf"
FILE="C:\Temp\foo.pdf"
DELETEFILE="No">
<CFSETTING ENABLECFOUTPUTONLY="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]
