对 PUT 方法的支持

PHP 3 和 PHP 4 对 PUT 方法的支持有所不同。在 PHP 4 中，必须使用标准的输入流来读取一个 HTTP PUT 的内容。

例子 38-5. 用 PHP 4 来保存 HTTP PUT 文件
<?php /* PUT data comes in on the stdin stream */ $putdata = fopen("php://stdin", "r"); /* Open a file for writing */ $fp = fopen("myputfile.ext", "w"); /* Read the data 1 KB at a time and write to the file */ while ($data = fread($putdata, 1024)) fwrite($fp, $data); /* Close the streams */ fclose($fp); fclose($putdata); ?>

注: 以下文档的内容仅对 PHP 3 适用。

PHP 提供对诸如 Netscape Composer 和 W3C Amaya 等客户端使用的 HTTP PUT 方法的支持。PUT 请求比文件上传要简单的多，它们一般的形式为：

PUT /path/filename.html HTTP/1.1

这通常意味着远程客户端会将其中的 /path/filename.html 存储到 web 目录树。让 Apache 或者 PHP 自动允许所有人覆盖 web 目录树下的任何文件显然是很不明智的。因此，要处理类似的请求，必须先告诉 web 服务器需要用特定的 PHP 脚本来处理该请求。在 Apache 下，可以用 Script 选项来设置。它可以被放置到 Apache 配置文件中几乎所有的位置。通常我们把它放置在 <Directory> 区域或者 <Virtualhost> 区域。可以用如下一行来完成该设置：

Script PUT /put.php

这将告诉 Apache 将所有对 URI 的 PUT 请求全部发送到 put.php 脚本，这些 URI 必须和 PUT 命令中的内容相匹配。当然，这是建立在 PHP 支持 .php 扩展名，并且 PHP 已经在运行的假设之上。

在 put.php 文件中，可以作如下操作：


<?php copy($PHP_UPLOADED_FILE_NAME, $DOCUMENT_ROOT . $REQUEST_URI); ?>

这将会把文件拷贝到远程客户端请求的位置。可能希望在文件拷贝之前进行一些检查或者对用户认证之类的操作。这里唯一的问题是，当 PHP 接受到 PUT 方法的请求时，它将会把上传的文件储存到和其它用 POST 方法处理过的文件相同的临时目录。在请求结束时，临时文件将被删除。因此，用来处理 PUT 的 PHP 脚本必须将该文件拷贝到其它的地方。该临时文件的文件名被储存在变量 $PHP_PUT_FILENAME 中，也可以通过 $REQUEST_URI 变量获得建议的目标文件名（在非 Apache web 服务器上可能会有较大的变化）。该目标文件名是由远程客户端指定的。也可以不听从改客户端的信息，而把所有上传的文件存储到一个特殊的上传目录下。

add a note User Contributed Notes

yaogzhan at gmail dot com
14-Dec-2005 08:01


PUT raw data comes in php://input, and you have to use fopen() and fread() to get the content. file_get_contents() is useless. 



The HTTP PUT request MUST contain a Content-Length header to specify the length (in bytes) of the body, or the server will not be able to know when the input stream is over. This is the common problem for many to find the php://input empty if no such header available. 



This should make PUT work properly on win32 using PHP5.1.1 and apache2.

warhog at warhog dot net
21-Sep-2005 05:11


Here's my solution on my Note below



The .htacces-File



Options FollowSymLinks



RewriteEngine on

RewriteBase !!!The Path of your PUT-Upload-Folder, relative to the DocumentRoot!!!

RewriteRule ^index\.php$ - [L]

RewriteRule ^(.*)$ index.php?url=$1 [L]



index.php:

<?php



if ($_SERVER['REQUEST_METHOD'] == "PUT")

{ $f = fopen(basename($_SERVER['REQUEST_URI']), "w");

  $s = fopen("php://input", "r");

  while($kb = fread($s, 1024))

  { fwrite($f, $kb, 1024); }

  fclose($f);

  fclose($s);

  Header("HTTP/1.1 201 Created"); }

elseif ($_SERVER['REQUEST_METHOD'] == "GET")

{ readfile(basename($_SERVER['REQUEST_URI'])); }



?>



Testes with Apache 2 and PHP 5, php as a module (win32)

warhog at warhog dot net
21-Sep-2005 04:22


NOTE: The <Script>-Directive can not be placed in .htaccess files.



So if you're having shared webspace and no access to the apache-configuration file you will have little chance to make something like this work.



But you can solve the problem, using mod_rewrite (for Apache) - for further information see the documentation at http://httpd.apache.org/docs/2.0/mod/mod_rewrite.html

gherson
15-Aug-2005 05:16


A Case Study:  To set up publishing with Netscape 7.2 Composer to Apache/PHP, no need to use CGI (which I tried unsuccessfully for too long) or to alter Apache's httpd.conf.  I needed only to click Publish As, fill in put2disk.php as the filename (where its contents are the below), and fill in that file's dir as the "Publishing address".

XAMPP 1.4.14: Apache/2.0.54 (Win32) mod_ssl/2.0.54 OpenSSL/0.9.7g PHP/5.0.4.



<? // filename: put2disk.php.



//file_put_contents ("get_def.out", print_r (get_defined_vars(), TRUE)); // debugging



// Two slurp methods: (a) didn't work, (b) did.

//$stdin_rsc = fopen("php://input", "r");

//$putdata='';

//while ($putdata .= fread($stdin_rsc, 1024)); // a. Hangs the "Publishing..." dialog.

//while (!feof($stdin_rsc)) $putdata.=fread($stdin_rsc, 8192); // b. Worked, but file_get_contents is faster.

//fclose($stdin_rsc);



// All that's nec:

$putdata=file_get_contents('php://input'); // Not php://stdin! (When the ability to see error messages isn't available, the doc (this manual page) needs to be more accurate.)



file_put_contents("stdin.out",$putdata);

?>

gomez_NOSPAM_pixline_dot_net
19-Apr-2004 03:59


Trying to capture a PUT stream into a single variable seems not to be allowed, probably because of the non presence of some kind of EOF. In this way save a PUT request into a database isn't easy.



The only way I find would be output to a cache file, then either insert filename into db or read again its content and place it in some kind of query.

mikeb at mikebanahan dot com
04-Nov-2003 06:41


I have spent a lot of time trying to make PUT work with Apache 2.0.40. I have not yet been able to find any way of making the Script directive invoke php via mod_php, the only way has been to have a file called example.cgi and invoke it via CGI, with the file starting

#!/usr/bin/php

so the PHP interpreter is invoked through the CGI mechanism and not as a module.



If there IS a way of making it work 'right' I'd love to know! After six hours of messing around, I've settled for CGI. The error messages in the apache error log are significantly misleading and the whole thing has been an exercise in frustration.



Attempts to use AddHandler and all 'normal' ways of trying to persuade Apache to do this have been fruitless. It does seem as if PUT can only be handled by CGI invocation.

php at dreier dot nu
14-Feb-2003 02:21


I can only make it work when I am using PHP as CGI, not as an Apache module.

I am using the version of PHP/Apahce that is shipped with Debian/testing.



You have to load the action_module, but not the put_module in Apache config.

add a note