CVS update: php3/doc/chapters

Date: Friday June 4, 1999 @ 13:24 Author: eschmid Update of /repository/php3/doc/chapters In directory php:/tmp/cvs-serv24525 Modified Files: features.sgml Log Message: and done some formating. Index: php3/doc/chapters/features.sgml diff -u php3/doc/chapters/features.sgml:1.32 php3/doc/chapters/features.sgml:1.33 --- php3/doc/chapters/features.sgml:1.32 Fri Jun 4 13:18:41 1999 +++ php3/doc/chapters/features.sgml Fri Jun 4 13:24:30 1999 @@ -251,54 +251,57 @@ <sect1 id="feature-putsupport"> <title>PUT Method Support</title> <simpara> - PHP provides support for the HTTP PUT method used by clients such as - Netscape Composer and W3C Amaya. PUT requests are much - simpler than a file upload and they look something like this: + PHP provides support for the HTTP PUT method used by clients such + as Netscape Composer and W3C Amaya. PUT requests are much simpler + than a file upload and they look something like this: </simpara> <simpara> - <emphasis>PUT /path/filename.html HTTP/1.1</emphasis> + <emphasis>PUT /path/filename.html HTTP/1.1</emphasis> </simpara> <simpara> - This would normally mean that the remote client would like to save - the content that follows as: /path/filename.html in your web tree. - It is obviously not a good idea for Apache or PHP to automatically - let everybody overwrite any files in your web tree. So, to handle - such a request you have to first tell your web server that you want - a certain PHP script to handle the request. In Apache you do this - with the <emphasis>Script</emphasis> directive. It can be placed - almost anywhere in your Apache configuration file. A common place - is inside a &lt;Directory&gt; block or perhaps inside a &lt;Virtualhost&gt; - block. A line like this would do the trick: + This would normally mean that the remote client would like to save + the content that follows as: /path/filename.html in your web tree. + It is obviously not a good idea for Apache or PHP to automatically + let everybody overwrite any files in your web tree. So, to handle + such a request you have to first tell your web server that you + want a certain PHP script to handle the request. In Apache you do + this with the <emphasis>Script</emphasis> directive. It can be + placed almost anywhere in your Apache configuration file. A + common place is inside a &lt;Directory&gt; block or perhaps inside + a &lt;Virtualhost&gt; block. A line like this would do the trick: </simpara> <simpara> - <emphasis>Script PUT /put.php3</emphasis> + <emphasis>Script PUT /put.php3</emphasis> </simpara> <simpara> - This tells Apache to send all PUT requests for URIs that match the - context in which you put this line to the put.php3 script. This assumes, - of course, that you have PHP enabled for the .php3 extension and PHP is - active. + This tells Apache to send all PUT requests for URIs that match the + context in which you put this line to the put.php3 script. This + assumes, of course, that you have PHP enabled for the .php3 + extension and PHP is active. </simpara> <simpara> - Inside your put.php3 file you would then do something like this: + Inside your put.php3 file you would then do something like this: </simpara> <simpara> - &lt;? copy($PHP_UPLOADED_FILE_NAME,$DOCUMENT_ROOT.$REQUEST_URI); ?&gt; + &lt;? copy($PHP_UPLOADED_FILE_NAME,$DOCUMENT_ROOT.$REQUEST_URI); ?&gt; </simpara> <simpara> - This would copy the file to the location requested by the remote client. - You would probably want to perform some checks and/or authenticate the - user before performing this file copy. The only trick here is that when - PHP sees a PUT-method request it stores the uploaded file in a temporary - file just like the <link linkend="feature-fileupload">File Upload</link> - feature. When the request ends, this temporary file is deleted. So, your - PUT handling PHP script has to copy that file somewhere. The filename of - this temporary file is in the $PHP_PUT_FILENAME variable, and you can see - the suggested destination filename in the $REQUEST_URI (may vary on non-Apache - web servers). This destination filename is the one that the remote client - specified. You do not have to listen to this client. You could, for example, - copy all uploaded files to a special uploads directory. + This would copy the file to the location requested by the remote + client. You would probably want to perform some checks and/or + authenticate the user before performing this file copy. The only + trick here is that when PHP sees a PUT-method request it stores + the uploaded file in a temporary file just like the <link + linkend="feature-fileupload">File Upload</link> feature. When the + request ends, this temporary file is deleted. So, your PUT + handling PHP script has to copy that file somewhere. The filename + of this temporary file is in the $PHP_PUT_FILENAME variable, and + you can see the suggested destination filename in the $REQUEST_URI + (may vary on non-Apache web servers). This destination filename + is the one that the remote client specified. You do not have to + listen to this client. You could, for example, copy all uploaded + files to a special uploads directory. </simpara> + </sect1> <sect1 id="feature-cookies"> <title>HTTP cookie support</title>