Your assumption is not correct. Files exist only as "tmp_name" as long as they have not been downloaded. As soon as you download the file only the "name" param can be found.

So it depends on when you call this method... before downloading the file or afterwards. But the method itself does not know if you already downloaded the file or not. Therefor it checks if the given file exists or not to decide which action to use.

Then this is only a bug if we call this method before downloading the file (which is my use case). Is there a precondition on calling receive() that the file must already have been downloaded, or is my use case supposed to be supported?

This is how I call the transfer:

  $upload = new Zend_File_Transfer('HttpFixed');
  $upload->receive();
  $path = $upload->getFileName();
  $filesize =  filesize($path);
  $filename = $upload->getFilename(null, false);

Then, I call a method that copies the posted file into a path corresponding to its md5sum, so no file exists by its original uploaded name.

Ignore the 'HttpFixed', that was my workaround subclass adapter.

In my opinion this can not work.

You are creating a file transfer according to the given $_FILES variable from a form. Then you say "download this files" by calling receive()... but then you say that !afterwards! you copy the file into another path... and the class should know that changed path before you set it???

You eighter set the name and path before you receive the file (with the rename filter) or you set it manually.

The problem is happening in the very first line.

$upload = new Zend_File_Transfer();

It's actually the very first line of my controller.

Everything after that is actually working fine. The only thing failing is the mime type check. The constructor calls _prepareFiles, which is calling _detectMimeType, which is failing because it's checking if the file exists by name (in the current working directory, which is my application root dir) before it checks the existence of the tmp_name file. If we just switched the order of checking that existence, it would actually work for me. To reproduce this bug, just create a minimal zend application, place a dummy.txt file in the root directory of it, create a controller that just calls that one line of code, and then attempt to upload a different file called dummy.txt.

This block of code is the culprit:

protected function _detectMimeType($value) { if (file_exists($value['name'])) { $file = $value['name']; } else if (file_exists($value['tmp_name'])) { $file = $value['tmp_name']; }

I think that is meant to be equivalent to:

if(file_already_moved_from_tmp_name)
      $file= $value['name'];
else if(file_exists($value['tmp_name']))
      $file = $value['tmp_name'];

But they are not equivalent, because file_exists($value['name']) does not represent the condition that the file has already been downloaded; especially since this is happening in the constructor, so we know the file has not already been received.

Any status update on this issue?

Thanks,

-Zach

Are there plans to fix this in the next release?