From 000de17b6f6916be249b827132a35967da0064c8 Mon Sep 17 00:00:00 2001
From: Jakub Vrana <vrana@php.net>
Date: Fri, 23 Mar 2007 15:03:09 +0000
Subject: [PATCH] Clarify that secure relates to client (bug #40778)

git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@232437 c90b9560-bf6c-de11-be94-00142212c4b1
---
 reference/network/functions/setcookie.xml | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/reference/network/functions/setcookie.xml b/reference/network/functions/setcookie.xml
index abdb76a014..0490f12323 100644
--- a/reference/network/functions/setcookie.xml
+++ b/reference/network/functions/setcookie.xml
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.4 $ -->
+<!-- $Revision: 1.5 $ -->
 <!-- splitted from ./en/functions/http.xml, last change in rev 1.2 -->
   <refentry id="function.setcookie">
    <refnamediv>
@@ -136,9 +136,11 @@
          <entry><parameter>secure</parameter></entry>
          <entry>
           Indicates that the cookie should only be transmitted over a 
-          secure HTTPS connection. When set to &true;, the
+          secure HTTPS connection from the client. When set to &true;, the
           cookie will only be set if a secure connection exists. The default
-          is &false;.
+          is &false;. On the server-side, it's on the programmer to send this
+          kind of cookie only on secure connection (e.g. with respect to
+          <literal>$_SERVER["HTTPS"]</literal>).
          </entry>
          <entry>
           &true; or &false;