From 008af441d7702a1e347c9d269aa54119f389b038 Mon Sep 17 00:00:00 2001 From: Alexander Voytsekhovskyy Date: Mon, 24 May 2004 19:24:53 +0000 Subject: [PATCH] change line ending to \n git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@159525 c90b9560-bf6c-de11-be94-00142212c4b1 --- features/cookies.xml | 126 +++++++++++++++++++++---------------------- 1 file changed, 63 insertions(+), 63 deletions(-) diff --git a/features/cookies.xml b/features/cookies.xml index ef9f88c3ec..e7820a4dce 100644 --- a/features/cookies.xml +++ b/features/cookies.xml @@ -1,63 +1,63 @@ - - - - Cookies - - - &php; transparently supports HTTP cookies. Cookies are a - mechanism for storing data in the remote browser and thus tracking or - identifying return users. You can set cookies using the - setcookie or setrawcookie - function. Cookies are part of the HTTP header, so - setcookie must be called before any output is sent to - the browser. This is the same limitation that header - has. You can use the output buffering - functions to delay the script output until you have decided whether - or not to set any cookies or send any headers. - - - - Any cookies sent to you from the client will automatically be turned into a - &php; variable just like GET and POST - method data, depending on the register_globals - and variables_order - configuration variables. If you wish to assign multiple values to a single - cookie, just add [] to the cookie name. - - - - In &php; 4.1.0 and later, the $_COOKIE auto-global array - will always be set with any cookies sent from the client. - $HTTP_COOKIE_VARS is also set in earlier versions of &php; - when the track_vars configuration - variable is set. (This setting is always on since &php; 4.0.3.) - - - - For more details, including notes on browser bugs, see the - setcookie and setrawcookie - function. - - - - - + + + + Cookies + + + &php; transparently supports HTTP cookies. Cookies are a + mechanism for storing data in the remote browser and thus tracking or + identifying return users. You can set cookies using the + setcookie or setrawcookie + function. Cookies are part of the HTTP header, so + setcookie must be called before any output is sent to + the browser. This is the same limitation that header + has. You can use the output buffering + functions to delay the script output until you have decided whether + or not to set any cookies or send any headers. + + + + Any cookies sent to you from the client will automatically be turned into a + &php; variable just like GET and POST + method data, depending on the register_globals + and variables_order + configuration variables. If you wish to assign multiple values to a single + cookie, just add [] to the cookie name. + + + + In &php; 4.1.0 and later, the $_COOKIE auto-global array + will always be set with any cookies sent from the client. + $HTTP_COOKIE_VARS is also set in earlier versions of &php; + when the track_vars configuration + variable is set. (This setting is always on since &php; 4.0.3.) + + + + For more details, including notes on browser bugs, see the + setcookie and setrawcookie + function. + + + + +