Description: ------------ I think it would be a great idea to include a new member in HTTP_Upload_File where to save the hash of the uploaded file.

Which type of hash would you like? md5, sha-1, sha-256? maybe a different one? What is so hard about computing it yourself? Many people don't need this, so always calculating the hash would be wasted CPU time for most.

Sorry for bothering you with such nonsenses. Thanks for your "kind" response. I've already done it by myself, but I think that HTTP_Upload would improve its API offering this new feature. Therefore, it seems quite useful to contain the hash and the file in the same object "for free", doesn't it? But as I said before, I've already done it.

You still did not tell us what kind of hash you would like to have - and how you would go about the possibility that other people would need different types of hashes. How would you do that?

There are two reasons why to implement it: 1. The administrator could be able to check the integrity of the file in the server once uploaded. 2. The application Web user could be able to check the integrity of the selected file to download. Therefore, this new feature would improve the security of the application Web. Of course, this checking has an impact in the performance. I'm currently using sha1 (see the function sha1_file), but I'd like to move to sha256. I haven't studied it yet. I'd never use md5.