PHP: Supporto per metodo PUT

Supporto per metodo PUT

PHP fornisce supporto per il metodo HTTP PUT utilizzato da alcuni client per caricare i file sul server. Le richieste PUT sono molto più semplici rispetto al caricamento di un file attraverso POST, e assomigliano a

PUT /percorso/nomefile.html HTTP/1.1

Questo significa che normalmente il programma remoto intende salvare il contenuto della richesta come : /path/filename.html nel filesystem sul server web. Non è ovviamente una buona idea per Apache o PHP lasciare a un qualsiasi utente la possibilità di sovrascrivere file sul server web. Quindi, per gestire questa richiesta si deve chiedere al server web che si vuole che sia un certo script PHP a gestire la richiesta stessa. In Apache si ottiene questo con la direttiva Script. Può essere posta quasi ovunque nel file di configurazione di Apache. Un posto frequente è all'interno di un blocco <Directory> oppurte all'interno del blocco <Virtualhost>. Un linea come la seguente è sufficiente:

Script PUT /put.php

Questo chiede ad Apache di inviare tutte le richieste PUT che soddisfano il contesto in cui si è inserito questo comando allo script put.php. Questo richiede, naturalmente, che sia abilitato PHP per l'estensione .php e che PHP sia attivo. La risorsa di destinazione per tutte le richieste PUT verso questo script deve essere lo script stesso, non in nome di file che si desidera caricare.

All'interno del file put.php si può inserire qualcosa simile al seguente esempio. Questo copia il contenuto del file caricato verso il file myputfile.ext sul server. È consigliabile attuare dei controlli e/o autenticare l'utilizzatore prima di eseguire la copia del file.

Example #1 Registrare i file ricevuti con HTTP PUT

<?php
/* i dati PUT arrivano sull stream stdin */
$putdata = fopen("php://input", "r");

/* Apre il file in scrittura */
$fp = fopen("myputfile.ext", "w");

/* Legge i dati 1 KB alla volta
   e scrive sul file */
while ($data = fread($putdata, 1024))
  fwrite($fp, $data);

/* Chiude gli stream */
fclose($fp);
fclose($putdata);
?>

Found A Problem?

Learn How To Improve This Page • Submit a Pull Request • Report a Bug

＋add a note

User Contributed Notes 6 notes

down

micronix at gmx dot net ¶

14 years ago

Hello PHP World After many Hours of worryness :=)



I have found the Solution for Resume or Pause Uploads

In this Code Snippet it is the Server Side not Client on any Desktop Programm you must use byte ranges to calculate the uploaded bytes and missing of total bytes.



Here the PHP Code



<?php

$CHUNK = 8192;



        try {

            if (!($putData = fopen("php://input", "r")))

                throw new Exception("Can't get PUT data.");



            // now the params can be used like any other variable

            // see below after input has finished



            $tot_write = 0;

            $tmpFileName = "/var/dev/tmp/PUT_FILE";

            // Create a temp file

            if (!is_file($tmpFileName)) {

                fclose(fopen($tmpFileName, "x")); //create the file and close it

                // Open the file for writing

                if (!($fp = fopen($tmpFileName, "w")))

                    throw new Exception("Can't write to tmp file");



                // Read the data a chunk at a time and write to the file

                while ($data = fread($putData, $CHUNK)) {

                    $chunk_read = strlen($data);

                    if (($block_write = fwrite($fp, $data)) != $chunk_read)

                        throw new Exception("Can't write more to tmp file");



                    $tot_write += $block_write;

                }



                if (!fclose($fp))

                    throw new Exception("Can't close tmp file");



                unset($putData);

            } else {

                // Open the file for writing

                if (!($fp = fopen($tmpFileName, "a")))

                    throw new Exception("Can't write to tmp file");



                // Read the data a chunk at a time and write to the file

                while ($data = fread($putData, $CHUNK)) {

                    $chunk_read = strlen($data);

                    if (($block_write = fwrite($fp, $data)) != $chunk_read)

                        throw new Exception("Can't write more to tmp file");



                    $tot_write += $block_write;

                }



                if (!fclose($fp))

                    throw new Exception("Can't close tmp file");



                unset($putData);

            }



            // Check file length and MD5

            if ($tot_write != $file_size)

                throw new Exception("Wrong file size");



            $md5_arr = explode(' ', exec("md5sum $tmpFileName"));

            $md5 = $md5sum_arr[0];

            if ($md5 != $md5sum)

                throw new Exception("Wrong md5");

        } catch (Exception $e) {

            echo '', $e->getMessage(), "\n";

        }

?>

down

arnaud at caramia dot Fr ¶

1 year ago

We resolved our problem with https://pecl.php.net/package/apfd.

It parses multipart/form-data body (files and payload) with PUT and PATCH http requests, witch was only possible before with POST http request.

down

Oscar Fernandez Sierra ¶

3 years ago

This is what worked for me. There are many examples in the web that don't work. I found in https://lornajane.net/posts/2009/putting-data-fields-with-php-curl.

IMPORTANT: You should not use the code

       curl_setopt($ch, CURLOPT_PUT, true);

even if it seems to be the right option (it would be the right option for a POST request, with CURLOPT_POST, but it does not work for a PUT request).

Notice that the constant CURLOPT_CUSTOMREQUEST is used instead of CURLOPT_PUT, and that the value used is "PUT" instead of true.

<?php

        $url = "....."; // put your URL here

        $data = array("a" => $a);

        $ch = curl_init($url);
        curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
        curl_setopt($ch, CURLOPT_CUSTOMREQUEST, "PUT");
        curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($data));

        $response = curl_exec($ch);
        if ( ! $response) {
            return false;
        }

down

polygon dot co dot in at gmail dot com ¶

1 year ago

I was confused with file uploads using the PUT method.
My concern was why can't we upload multiple files using the PUT method with streams
PUT data comes in on the stdin stream
$putdata = fopen("php://input", "r");
Note the $putdata is a file pointer to the file content that is being uploaded.
The data is received on the server on the fly (which means available as it is received)

Secondly, when we are using parse_str(file_get_contents("php://input")).
This means the data is completely received on the server end and is then made available to the script.

When using fopen() one cant parse the data. This can be used when uploading a large file.
The file may range from 100's of MBs to Gigs where streams plays a major role.

Streams make the file data available to script in chunks instead of first saving in the temp folder.
Hence, when using $putdata = fopen("php://input", "r"); one can't pass the payload as well.
If someone wants to pass the payload the only option is in the URL query string.

down

San ¶

10 years ago

Instead of using fread fwrite to save uploaded content to a file.
stream_copy_to_stream is much cleaner.

down

willy at kochkonsult dot no ¶

3 years ago

All the example code I found for using PUT with PHP always used a default hard-coded file extension for the incoming stream.

The filename from the incoming file PUT request can't be found anywhere from the incoming request (at least I couldn't find it) but mimetype can be found in the $_SERVER global variable.

I used this code to get the correct file extension:

$mimeType = $_SERVER['HTTP_CONTENT_TYPE'];

if ($mimeType!='application/pdf') 
    {   
    header('HTTP/1.1 405 Only PDF files allowed');
    echo("Only PDF files are allowed for upload - this file is ".$mimeType);
    die();
    }
else $fileExtension = 'pdf';

If you have an Apache Tika server available, that would be the best option to analyze the file content to get the mimetype, but that might not be in scope for everyone :-)

＋add a note