We use the cfcontent tag as well. We have our
documents stored in binary in the database so we just
run a query to pull the data out and then use the
cfcontent tag :
cfheader name=content-disposition
value=attachment; filename=#docName#
cfcontent type=#DocEXTMime#
variable=#DocBinData#
--- Mike
On 2/21/08, Darin Kohles [EMAIL PROTECTED] wrote:
if you absolutely want to give the full URL, then
use the format 'http://yourdomain.com/' - as the file(s) will have to
be located relative to your web root.
Yep. This is the method I've followed in the past. I've found that there are
a lot
How do you then control unauthorized access to the file? How do you
know when to delete the file?
-dhs
Dean H. Saxe, CISSP, CEH
[EMAIL PROTECTED]
[T]he people can always be brought to the bidding of the leaders.
This is easy. All you have to do is to tell them they are being
attacked,
The only problems I have ever seen with cfcontent and setting the doc type
is that people get confused that things just open however, they forget
that they actually told their browser to do this at some point when they
installed software. So i usually end up sending pdf's or whatever and
forcing
Well sure, you have to balance those concerns, it depends on the sensitivity
of your output. If you need to control access to the files, assuming you
had an authenticated user system, you could have an output directory per
user or group and authenticate the user's access to that directory in
In regards unauthorized access, one work-around that I've built in the
past was the following: In a typical CMS, most managed file content is
abstracted into an ID based folder and file structure; these ID's are
stored in the database along with a friendly name. When a user wants
access to the
yikes what about this?
cfheader name=Content-Disposition value=attachment;
filename=#fomattedName#
On Fri, Feb 22, 2008 at 5:05 PM, Darin Kohles [EMAIL PROTECTED] wrote:
In regards unauthorized access, one work-around that I've built in the
past was the following: In a typical CMS, most
To: discussion@acfug.org
Subject: Re: [ACFUG Discuss] Newbie's Next Daunting Dilemma
Another thought I had is why not use the cfcontent tag? I tend to use
that tag when I want to obscure file paths from users while displaying
things like pdfs. You could open a new window and always have it use
the same
You definately do NOT want to include the absolute path 'C:/' - use
relative paths, or if you absolutely want to give the full URL, then
use the format 'http://yourdomain.com/' - as the file(s) will have to
be located relative to your web root.
On Thu, Feb 21, 2008 at 9:49 PM, Peyton Todd [EMAIL
This one ought to be easy for someone who knows how. I want to load a pdf into
a web page child window. When I put the pdf on the website's directory, the
following code (where the function is passed a job number naming the pdf) works
without a hitch:
function ScannedStyle(jn){
jn = jn +
Another thought I had is why not use the cfcontent tag? I tend to use
that tag when I want to obscure file paths from users while displaying
things like pdfs. You could open a new window and always have it use
the same cfm file while passing a variable into it via a url or
something so it
11 matches
Mail list logo
