tularis Sun Jan 2 09:41:46 2005 EDT
Modified files:
/phpdoc/en/reference/http/functions setcookie.xml
Log:
integrated a couple of notes
http://cvs.php.net/diff.php/phpdoc/en/reference/http/functions/setcookie.xml?r1=1.33&r2=1.34&ty=u
Index: phpdoc/en/reference/http/functions/setcookie.xml
diff -u phpdoc/en/reference/http/functions/setcookie.xml:1.33
phpdoc/en/reference/http/functions/setcookie.xml:1.34
--- phpdoc/en/reference/http/functions/setcookie.xml:1.33 Fri Oct 29
05:03:30 2004
+++ phpdoc/en/reference/http/functions/setcookie.xml Sun Jan 2 09:41:45 2005
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.33 $ -->
+<!-- $Revision: 1.34 $ -->
<!-- splitted from ./en/functions/http.xml, last change in rev 1.2 -->
<refentry id="function.setcookie">
<refnamediv>
@@ -314,20 +314,18 @@
</para>
<note>
<para>
- For more information on cookies, see Netscape's cookie
- specification at <ulink
- url="&spec.cookies;">&spec.cookies;</ulink> and
- <ulink url="&url.rfc;2965">RFC 2965</ulink>.
- </para>
- <para>
- You may notice the <parameter>expire</parameter> parameter takes on a
- Unix timestamp, as opposed to the date format <literal>Wdy, DD-Mon-YYYY
- HH:MM:SS GMT</literal>, this is because PHP does this conversion
- internally.
- </para>
- <para>
- <parameter>expire</parameter> is compared to the client's time which can
- differ from server's time.
+ The following RFC's may also be useful:
+ <ulink url="&url.rfc;2109">RFC 2109</ulink> and
+ <ulink url="&url.rfc;2965">RFC 2695</ulink>
+ <para>
+ You may notice the <parameter>expire</parameter> parameter takes on a
+ Unix timestamp, as opposed to the date format <literal>Wdy, DD-Mon-YYYY
+ HH:MM:SS GMT</literal>, this is because PHP does this conversion
+ internally.
+ </para>
+ <para>
+ <parameter>expire</parameter> is compared to the client's time which can
+ differ from server's time.
</para>
</note>
<note>
