From 45c08109f58c3603b8e61468d8ba2392a70ac45f Mon Sep 17 00:00:00 2001
From: Philip Olson <philip@php.net>
Date: Sat, 18 Jan 2003 09:34:57 +0000
Subject: [PATCH] Document that safe_mode_include_dir are paths, not directory
 names.  Essentially copied the docs from open_basedir.  This closes bug
 #16685

git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@112363 c90b9560-bf6c-de11-be94-00142212c4b1
---
 features/safe-mode.xml | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/features/safe-mode.xml b/features/safe-mode.xml
index 48859470af..e779a30316 100644
--- a/features/safe-mode.xml
+++ b/features/safe-mode.xml
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.28 $ -->
+<!-- $Revision: 1.29 $ -->
  <chapter id="features.safe-mode">
   <title>Safe Mode</title>
 
@@ -121,6 +121,13 @@
         <link linkend="ini.include-path">include_path</link> directive,
         rather than just a single directory.
        </simpara>
+       <simpara>
+        The restriction specified is actually a prefix, not a directory name. 
+        This means that "safe_mode_include_dir = /dir/incl" also allows
+        access to "/dir/include" and "/dir/incls" if they exist.  When you 
+        want to restrict access to only the specified directory, end with a 
+        slash. For example: "safe_mode_include_dir = /dir/incl/"
+       </simpara>
       </listitem>
      </varlistentry>
      <varlistentry id="ini.safe-mode-exec-dir">