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, and denounce the pacifists for lack of patriotism and
exposing the country to danger. It works the same in every country."
--Hermann Goering, Hitler's Reich-Marshall at the Nuremberg Trials
On Feb 22, 2008, at 8:41 AM, Howard Fore wrote:
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 of pitfalls with the cfcontent and cfheader in
getting cross-browser acceptability of various document types using
MIME types, particularly when you get into the issue of wanting the
downloaded file to have a specific file name. Your Mileage May Vary.
So the process I've followed is to write the file to disk in an
internet accessible location (ie, somewhere in your webroot), then
send the browser a page that has a javascript function that sets the
location.href to that file.
--
Howard Fore, [EMAIL PROTECTED]
"The universe tends toward maximum irony. Don't push it." - Jeff
Atwood
-------------------------------------------------------------
Annual Sponsor - Figleaf Software
To unsubscribe from this list, manage your profile @
http://www.acfug.org?fa=login.edituserform
For more info, see http://www.acfug.org/mailinglists
Archive @ http://www.mail-archive.com/discussion%40acfug.org/
List hosted by FusionLink
-------------------------------------------------------------
