cvs: phpdoc /en/reference/session reference.xml

sas Sun Jan 26 10:19:02 2003 EDT Modified files: /phpdoc/en/reference/session reference.xml Log: add note Index: phpdoc/en/reference/session/reference.xml diff -u phpdoc/en/reference/session/reference.xml:1.28 phpdoc/en/reference/session/reference.xml:1.29 --- phpdoc/en/reference/session/reference.xml:1.28 Sat Jan 18 00:52:05 2003 +++ phpdoc/en/reference/session/reference.xml Sun Jan 26 10:19:02 2003 @@ -1,5 +1,5 @@ <?xml version="1.0" encoding="iso-8859-1"?> -<!-- $Revision: 1.28 $ --> +<!-- $Revision: 1.29 $ --> <reference id="ref.session"> <title>Session handling functions</title> <titleabbrev>Sessions</titleabbrev> @@ -73,7 +73,7 @@ convenience for the user. For example, if you want to protect users from simple social engineering tactics, you need to enable session.use_only_cookies. In that case, cookies must be enabled - unconditionally. + unconditionally on the user side, or sessions will not work. </para> <para> There are several ways to leak an existing session id to third parties.