Well I wouldn't suggest FTP'ing the file unless you want to add to your
headaches by actually setting up an FTP server.. This isn't PHP - its
really just html
You can set up an href that will download
as <A href="http://12.12.12.100/something/xyz.file">Give me some XYZ!</A>
if you really want to force feed your download, use the headers that you
had before, but test the fopen - thats just good programming e.g..
I am not changing your headers, I assume they are appropriate for
your file. I would have to check my notes to see if content length is
required.
Note that I am also testing for open on fopen. You should actually test
to result on fpassthru which will return false if something goes wrong,
but lets not get carried away here :)
//
//
$fp=fopen("$path/$filename","r");
if($fp) {
header("Content-Type: application/octet-stream");
header("Content-Disposition: attachment; filename=$filename");
header("Content-Length: ".filesize("$path/$filename"));
header("Pragma: no-cache");
header("Expires: 0");
fpassthru($fp);
// fpassthru just spits out to stdout and
// closes the handle for you
}
else {
print("Dang me! I couldn't open $filename I feel Soooo sad!<br>");
}
I can't be sure. I am learning PHP too, but I rather doubt that print()
will handle a binary stream properly and in either case, it makes no
sense to read the file - especially if it is big - into a buffer just to
turn around and write it back out again. If there were no fpassthru()
function, it would make sense to write one using a fread/fwrite() loop.
But this type of thing is exactly what fpassthru was added to PHP for....
