From 2d7fe59935a40c5d02218ca6cfaaaaa1d3728445 Mon Sep 17 00:00:00 2001 From: Aaron Schulz Date: Mon, 1 Apr 2013 16:39:36 -0700 Subject: [PATCH] [FileBackend] Clarified the noAccess/noListing docs a bit. Change-Id: I3f008e3d1931423fc3c73af587d657040fdffe83 --- includes/filebackend/FileBackend.php | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/includes/filebackend/FileBackend.php b/includes/filebackend/FileBackend.php index d0020dac41..d505d6fa88 100644 --- a/includes/filebackend/FileBackend.php +++ b/includes/filebackend/FileBackend.php @@ -682,6 +682,8 @@ abstract class FileBackend { * The 'noAccess' and 'noListing' parameters works the same as in secure(), * except they are only applied *if* the directory/container had to be created. * These flags should always be set for directories that have private files. + * However, setting them is not guaranteed to actually do anything. + * Additional server configuration may be needed to achieve the desired effect. * * @param array $params * $params include: @@ -709,7 +711,9 @@ abstract class FileBackend { * the container it belongs to. FS backends might add .htaccess * files whereas key/value store backends might revoke container * access to the storage user representing end-users in web requests. - * This is not guaranteed to actually do anything. + * + * This is not guaranteed to actually make files or listings publically hidden. + * Additional server configuration may be needed to achieve the desired effect. * * @param array $params * $params include: @@ -739,6 +743,9 @@ abstract class FileBackend { * access to the storage user representing end-users in web requests. * This essentially can undo the result of secure() calls. * + * This is not guaranteed to actually make files or listings publically viewable. + * Additional server configuration may be needed to achieve the desired effect. + * * @param array $params * $params include: * - dir : storage directory -- 2.20.1