On Thursday, February 27, 2003, at 10:55 AM, Gyepi SAM wrote:
I used the 'Content-Disposition' header [1] for a long time, but
eventually gave
up and simply appended the filename to the url because some versions
of IE ignore the
the headers altogether. I think it was a workaround to fix the
On Thursday, February 27, 2003, at 11:00 AM, Jay Powers wrote:
I have always used the following in the header.
Content-Disposition: attachment; filename=thefile.txt
So would I do something like:
print $q-header('application/zip; filename=myfile.zip');
?
Thanks,
Ricky
At 10:16 AM -0500 2/27/03, Richard Morse wrote:
On Thursday, February 27, 2003, at 08:03 AM, Bob Mariotti wrote:
1) no dialog box appears and the file is automatically downloaded
and stored in some obscure directory somewhere where the user
cannot find it; ow 2) a dialog box will appear but
On Thu, Feb 27, 2003 at 10:16:50AM -0500, Richard Morse wrote:
But if you do find a solution for setting the filename, I'd like to
know...
I seem to remember something about a Content-disposition header that can
do this? Something like:
Content-disposition: file; filename=prog.exe
I believe
On Thu, Feb 27, 2003 at 10:16:50AM -0500, Richard Morse wrote:
On Thursday, February 27, 2003, at 08:03 AM, Bob Mariotti wrote:
1) no dialog box appears and the file is automatically downloaded and
stored in some obscure directory somewhere where the user cannot find
it; ow 2) a dialog
This is what if have used. I have to admit I haven't tested it in all
the scenarios.
$query-header(-Type='application/zip','Content-
Disposition'='attachment;filename=myfile.zip');
Jay
On Thu, 2003-02-27 at 11:21, Richard Morse wrote:
On Thursday, February 27, 2003, at 11:00 AM,
hi
( 03.02.27 08:03 -0500 ) Bob Mariotti:
When the user select the data desired to be downloaded from the page our
perl programs issue a content-type: directive.
have you tried:
application/octet-stream
and using the content-disposition header?
--
.--- ... [ x ]
On Thursday, February 27, 2003, at 01:10 PM, Gyepi SAM wrote:
That url won't do what you want. This one should:
http://.../my_script.cgi/filename.ext?null=null
1. I only keep the null=null parameter because you claim it is
necessary.
2. I assume that your webserver can separate path info
On Thu, Feb 27, 2003 at 01:38:23PM -0500, Richard Morse wrote:
On Thursday, February 27, 2003, at 01:10 PM, Gyepi SAM wrote:
That url won't do what you want. This one should:
http://.../my_script.cgi/filename.ext?null=null
I think that I tried this a while ago, but it didn't work.
