Note that there are some explanatory texts on larger screens.

plurals
  1. POphp upload very large file best practice
    primarykey
    data
    text
    <p>There are many questions with this title , but no one helps. My application should handle file uploads with size up to 2 GB and it should be done through a browser , not something like a FTP file uploader.<br> I'm aware of configuration settings should be done for example on <code>php.ini</code> . but there are some questions in my mind : </p> <ol> <li><p>Is something like <strong>uploadify</strong> library a good solution for this file size or there are better alternatives? </p></li> <li><p>because of the big size , maybe this is desirable to have <strong>pause/resume</strong> functionality in it. is it possible to implement this functionality through HTTP file transfer via a browser? if yes , how to? </p></li> <li><p>some people talk about some type of vulnerabilities like <strong>DOS ATTACKS</strong>. is it in this case a serious issue and what are the considerations for this types of attacks? </p></li> </ol> <p>if there are any extra recommendations and suggestion , please tell me about them. </p> <p><strong>UPDATE:</strong> some have suggested to do the job using FTP file upload. should it be done by dedicating each user a FTP account to let them upload files using FTP clients such as FileZilla ? if so , how incoming processes should be handled . for example I give each user a directory like <strong>/home/user1</strong> and he uploads his files into this directory. Now how should I fetch uploaded file data and save it to database according to user session data.<br> Generally , I mean how to script over this FTP file uploading system?<br> or if it is impossible please tell me. </p> <p>please help.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload