Rephrase comment about default ordering to clarify interaction between

default ordering and client preferences. tid50417

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1059582 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/docs/manual/mod/mod_autoindex.xml b/docs/manual/mod/mod_autoindex.xml
index f3f402a2ec3b332baa05468d5d9cd871dbef7da1..c24de983b606502eb113686d9ed0b993712609f1 100644 (file)
--- a/docs/manual/mod/mod_autoindex.xml
+++ b/docs/manual/mod/mod_autoindex.xml
@@ -975,12 +975,14 @@ Name|Date|Size|Description</syntax>
     and identifies the primary key. The secondary key is
     <em>always</em> the ascending filename.</p>
 
-    <p>You can force a directory listing to only be displayed in a
-    particular order by combining this directive with the <code><a
-    href="#indexoptions.suppresscolumnsorting"
-    >SuppressColumnSorting</a></code> index option; this will prevent
-    the client from requesting the directory listing in a different
-    order.</p>
+    <p>You can, if desired, prevent the client from reordering the list
+    by also adding the <code><a
+    href="#indexoptions.suppresscolumnsorting">SuppressColumnSorting</a></code> 
+    index option to remove the sort link from the top of the column,
+    along with the <code><a
+    href="#indexoptions.ignoreclient">IgnoreClient</a></code> index
+    option to prevent them from manually adding sort options to the
+    query string in order to override your ordering preferences.</p>
 </usage>
 </directivesynopsis>