mirror of
https://github.com/sigmasternchen/php-doc-en
synced 2025-03-16 00:48:54 +00:00
Looks now better.
git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@21173 c90b9560-bf6c-de11-be94-00142212c4b1
This commit is contained in:
parent
81cc49259d
commit
b7bbef7cc4
1 changed files with 110 additions and 93 deletions
|
@ -3,9 +3,10 @@
|
|||
<titleabbrev>HTTP</titleabbrev>
|
||||
|
||||
<partintro>
|
||||
<simpara>
|
||||
These functions let you manipulate the output sent back to the
|
||||
remote browser right down to the HTTP protocol level.</simpara>
|
||||
<simpara>
|
||||
These functions let you manipulate the output sent back to the
|
||||
remote browser right down to the HTTP protocol level.
|
||||
</simpara>
|
||||
</partintro>
|
||||
|
||||
<refentry id="function.header">
|
||||
|
@ -25,44 +26,57 @@
|
|||
header strings. See the <ulink url="&spec.http1.1;">HTTP 1.1
|
||||
Specification</ulink> for more information on raw http headers.
|
||||
<emphasis>Note:</emphasis> Remember that the
|
||||
<function>Header</function> function must be called before any actual
|
||||
output is sent either by normal HTML tags or from PHP. It is a very
|
||||
common error to read code with <function>include</function> or with
|
||||
auto_prepend and have spaces or empty lines in this code that force
|
||||
output before <function>header</function> is called.</para>
|
||||
|
||||
<para>
|
||||
There are two special-case header calls. The first is the "Location"
|
||||
header. Not only does it send this header back to the browser, it also returns
|
||||
a REDIRECT status code to Apache. From a script writer's point of view this
|
||||
should not be important, but for people who understand Apache internals it is
|
||||
important to understand.
|
||||
<informalexample><programlisting role="php">
|
||||
header("Location: http://www.php.net"); /* Redirect browser to PHP web site */
|
||||
exit; /* Make sure that code below does not get executed when we redirect. */
|
||||
</programlisting></informalexample></para>
|
||||
<para>
|
||||
The second special-case is any header that starts with the string, "HTTP/"
|
||||
(case is not significant). For example, if you have your ErrorDocument 404 Apache
|
||||
directive pointed to a PHP script, it would be a good idea to make sure that your
|
||||
PHP script is actually generating a 404. The first thing you do in your script should
|
||||
then be:
|
||||
<informalexample><programlisting role="php">
|
||||
header("http/1.0 404 Not Found");
|
||||
</programlisting></informalexample>
|
||||
</para>
|
||||
|
||||
<function>Header</function> function must be called before any
|
||||
actual output is sent either by normal HTML tags or from PHP. It
|
||||
is a very common error to read code with
|
||||
<function>include</function> or with auto_prepend and have spaces
|
||||
or empty lines in this code that force output before
|
||||
<function>header</function> is called.
|
||||
</para>
|
||||
<para>
|
||||
There are two special-case header calls. The first is the
|
||||
"Location" header. Not only does it send this header
|
||||
back to the browser, it also returns a REDIRECT status code to
|
||||
Apache. From a script writer's point of view this should not be
|
||||
important, but for people who understand Apache internals it is
|
||||
important to understand.
|
||||
<informalexample>
|
||||
<programlisting role="php">
|
||||
header ("Location: http://www.php.net"); /* Redirect browser
|
||||
to PHP web site */
|
||||
exit; /* Make sure that code below does
|
||||
not get executed when we redirect. */
|
||||
</programlisting>
|
||||
</informalexample>
|
||||
</para>
|
||||
<para>
|
||||
The second special-case is any header that starts with the
|
||||
string, "HTTP/" (case is not significant). For
|
||||
example, if you have your ErrorDocument 404 Apache directive
|
||||
pointed to a PHP script, it would be a good idea to make sure
|
||||
that your PHP script is actually generating a 404. The first
|
||||
thing you do in your script should then be:
|
||||
<informalexample>
|
||||
<programlisting role="php">
|
||||
header ("http/1.0 404 Not Found");
|
||||
</programlisting>
|
||||
</informalexample>
|
||||
</para>
|
||||
<para>
|
||||
PHP scripts often generate dynamic HTML that must not be cached
|
||||
by the client browser or any proxy caches between the server and the
|
||||
client browser. Many proxies and clients can be forced to disable
|
||||
caching with
|
||||
<informalexample><programlisting role="php">
|
||||
header("Expires: Mon, 26 Jul 1997 05:00:00 GMT"); // Date in the past
|
||||
header("Last-Modified: " . gmdate("D, d M Y H:i:s") . " GMT"); // always modified
|
||||
header("Cache-Control: no-cache, must-revalidate"); // HTTP/1.1
|
||||
header("Pragma: no-cache"); // HTTP/1.0
|
||||
</programlisting></informalexample></para>
|
||||
<informalexample>
|
||||
<programlisting role="php">
|
||||
header ("Expires: Mon, 26 Jul 1997 05:00:00 GMT"); // Date in the past
|
||||
header ("Last-Modified: " . gmdate("D, d M Y H:i:s") . " GMT");
|
||||
// always modified
|
||||
header ("Cache-Control: no-cache, must-revalidate"); // HTTP/1.1
|
||||
header ("Pragma: no-cache"); // HTTP/1.0
|
||||
</programlisting>
|
||||
</informalexample>
|
||||
</para>
|
||||
</refsect1>
|
||||
</refentry>
|
||||
|
||||
|
@ -88,92 +102,95 @@ header("http/1.0 404 Not Found");
|
|||
<emphasis>before</emphasis> any other headers are sent (this is a
|
||||
restriction of cookies, not PHP). This requires you to place
|
||||
calls to this function before any <literal><html></literal> or
|
||||
<literal><head></literal> tags.</para>
|
||||
|
||||
<literal><head></literal> tags.
|
||||
</para>
|
||||
<para>
|
||||
All the arguments except the <parameter>name</parameter> argument are
|
||||
optional. If only the name argument is present, the cookie by that
|
||||
name will be deleted from the remote client. You may also replace
|
||||
any argument with an empty string (<emphasis>""</emphasis>)
|
||||
in order to skip that argument. The <parameter>expire</parameter>
|
||||
and <parameter>secure</parameter> arguments are integers
|
||||
and cannot be skipped with an empty string. Use a zero
|
||||
(<emphasis>0</emphasis>) instead. The <parameter>expire</parameter>
|
||||
argument is a regular Unix time integer as returned by the
|
||||
<function>time</function> or <function>mktime</function> functions.
|
||||
The <parameter>secure</parameter> indicates that the cookie should
|
||||
only be transmitted over a secure HTTPS connection.</para>
|
||||
|
||||
All the arguments except the <parameter>name</parameter> argument
|
||||
are optional. If only the name argument is present, the cookie
|
||||
by that name will be deleted from the remote client. You may
|
||||
also replace any argument with an empty string
|
||||
(<emphasis>""</emphasis>) in order to skip that
|
||||
argument. The <parameter>expire</parameter> and
|
||||
<parameter>secure</parameter> arguments are integers and cannot
|
||||
be skipped with an empty string. Use a zero
|
||||
(<emphasis>0</emphasis>) instead. The
|
||||
<parameter>expire</parameter> argument is a regular Unix time
|
||||
integer as returned by the <function>time</function> or
|
||||
<function>mktime</function> functions. The
|
||||
<parameter>secure</parameter> indicates that the cookie should
|
||||
only be transmitted over a secure HTTPS connection.
|
||||
</para>
|
||||
<para>
|
||||
Common Pitfalls:</para>
|
||||
|
||||
Common Pitfalls:
|
||||
</para>
|
||||
<simpara>
|
||||
Cookies will not become visible until the next loading of a page that
|
||||
the cookie should be visible for.</simpara>
|
||||
|
||||
the cookie should be visible for.
|
||||
</simpara>
|
||||
<simpara>
|
||||
Multiple calls to <function>setcookie</function> in the same
|
||||
script will be performed in reverse order. If you are trying to
|
||||
delete one cookie before inserting another you should put the
|
||||
insert before the delete.</simpara>
|
||||
|
||||
insert before the delete.
|
||||
</simpara>
|
||||
<para>
|
||||
Some examples follow:
|
||||
<example>
|
||||
<title><function>setcookie</function> examples</title>
|
||||
<programlisting role="php">
|
||||
setcookie("TestCookie","Test Value");
|
||||
setcookie("TestCookie",$value,time()+3600); /* expire in 1 hour */
|
||||
setcookie("TestCookie",$value,time()+3600,"/~rasmus/",".utoronto.ca",1);
|
||||
</programlisting></example></para>
|
||||
|
||||
setcookie ("TestCookie", "Test Value");
|
||||
setcookie ("TestCookie", $value,time()+3600); /* expire in 1 hour */
|
||||
setcookie ("TestCookie", $value,time()+3600, "/~rasmus/", ".utoronto.ca", 1);
|
||||
</programlisting>
|
||||
</example>
|
||||
</para>
|
||||
<para>
|
||||
Note that the value portion of the cookie will automatically be
|
||||
urlencoded when you send the cookie, and when it is received, it
|
||||
is automatically decoded and assigned to a variable by the same
|
||||
name as the cookie name. To see the contents of our test
|
||||
cookie in a script, simply use one of the following examples:
|
||||
|
||||
<informalexample><programlisting role="php">
|
||||
<informalexample>
|
||||
<programlisting role="php">
|
||||
echo $TestCookie;
|
||||
echo $HTTP_COOKIE_VARS["TestCookie"];
|
||||
</programlisting></informalexample></para>
|
||||
|
||||
<para>
|
||||
You may also set array cookies by using array notation in the
|
||||
cookie name. This has the effect of setting as many cookies as
|
||||
you have array elements, but when the cookie is received by your
|
||||
script, the values are all placed in an array with the cookie's
|
||||
name:
|
||||
<informalexample>
|
||||
<programlisting role="php">
|
||||
setcookie( "cookie[three]", "cookiethree" );
|
||||
setcookie( "cookie[two]", "cookietwo" );
|
||||
setcookie( "cookie[one]", "cookieone" );
|
||||
if ( isset( $cookie ) ) {
|
||||
while( list( $name, $value ) = each( $cookie ) ) {
|
||||
echo "$name == $value<br>\n";
|
||||
}
|
||||
</programlisting>
|
||||
</informalexample>
|
||||
</para>
|
||||
<para>
|
||||
You may also set array cookies by using array notation in the
|
||||
cookie name. This has the effect of setting as many cookies as
|
||||
you have array elements, but when the cookie is received by your
|
||||
script, the values are all placed in an array with the cookie's
|
||||
name:
|
||||
<informalexample>
|
||||
<programlisting role="php">
|
||||
setcookie ("cookie[three]", "cookiethree");
|
||||
setcookie ("cookie[two]", "cookietwo");
|
||||
setcookie ("cookie[one]", "cookieone");
|
||||
if (isset ($cookie)) {
|
||||
while (list ($name, $value) = each ($cookie)) {
|
||||
echo "$name == $value<br>\n";
|
||||
}
|
||||
}
|
||||
</programlisting>
|
||||
</informalexample>
|
||||
|
||||
</para>
|
||||
|
||||
</programlisting>
|
||||
</informalexample>
|
||||
</para>
|
||||
<para>
|
||||
For more information on cookies, see Netscape's cookie
|
||||
specification at <ulink url="&spec.cookies;">&spec.cookies;</ulink>.</para>
|
||||
|
||||
specification at <ulink
|
||||
url="&spec.cookies;">&spec.cookies;</ulink>.
|
||||
</para>
|
||||
<simpara>
|
||||
Microsoft Internet Explorer 4 with Service Pack 1 applied does
|
||||
not correctly deal with cookies that have their path parameter
|
||||
set.</simpara>
|
||||
|
||||
set.
|
||||
</simpara>
|
||||
<simpara>
|
||||
Netscape Communicator 4.05 and Microsoft Internet Explorer 3.x
|
||||
appear to handle cookies incorrectly when the path and time
|
||||
are not set.</simpara>
|
||||
|
||||
are not set.
|
||||
</simpara>
|
||||
</refsect1>
|
||||
</refentry>
|
||||
|
||||
|
@ -189,7 +206,7 @@ sgml-always-quote-attributes:t
|
|||
sgml-indent-step:1
|
||||
sgml-indent-data:t
|
||||
sgml-parent-document:nil
|
||||
sgml-default-dtd-file:"../manual.ced"
|
||||
sgml-default-dtd-file:"../../manual.ced"
|
||||
sgml-exposed-tags:nil
|
||||
sgml-local-catalogs:nil
|
||||
sgml-local-ecat-files:nil
|
||||
|
|
Loading…
Reference in a new issue