[svnbook] r3780 committed - Indentation and whitespace changes only.

svnbook at googlecode.com svnbook at googlecode.com
Mon Sep 13 13:37:50 CDT 2010


Revision: 3780
Author: cmpilato at gmail.com
Date: Mon Sep 13 11:29:19 2010
Log: Indentation and whitespace changes only.
http://code.google.com/p/svnbook/source/detail?r=3780

Modified:
  /trunk/src/en/book/ch06-server-configuration.xml

=======================================
--- /trunk/src/en/book/ch06-server-configuration.xml	Mon Sep 13 11:27:21  
2010
+++ /trunk/src/en/book/ch06-server-configuration.xml	Mon Sep 13 11:29:19  
2010
@@ -3186,35 +3186,35 @@
        instead of doing global-search-and-replace operations on the
        whole access file.</para>

-  <!-- TODO(sussman): Once serf becomes officially support, this
-       sidebar will need to be revisited. -->
-
-  <sidebar>
-    <title>Partial Readability and Checkouts</title>
-
-    <para>If you're using Apache as your Subversion server and have
-      made certain subdirectories of your repository unreadable to
-      certain users, you need to be aware of a possible
-      nonoptimal behavior with <command>svn checkout</command>.</para>
-
-    <para>When the client requests a checkout or update over HTTP, it
-      makes a single server request and receives a single (often
-      large) server response.  When the server receives the request,
-      that is the <emphasis>only</emphasis> opportunity Apache has to
-      demand user authentication.  This has some odd side effects.
-      For example, if a certain subdirectory of the repository is
-      readable only by user Sally, and user Harry checks out a parent
-      directory, his client will respond to the initial authentication
-      challenge as Harry.  As the server generates the large response,
-      there's no way it can resend an authentication challenge when
-      it reaches the special subdirectory; thus the subdirectory is
-      skipped altogether, rather than asking the user to
-      reauthenticate as Sally at the right moment.  In a similar way,
-      if the root of the repository is anonymously world-readable,
-      the entire checkout will be done without
-      authentication—again, skipping the unreadable directory,
-      rather than asking for authentication partway through.</para>
-  </sidebar>
+    <!-- TODO(sussman): Once serf becomes officially support, this
+         sidebar will need to be revisited. -->
+    <sidebar>
+      <title>Partial Readability and Checkouts</title>
+
+      <para>If you're using Apache as your Subversion server and have
+        made certain subdirectories of your repository unreadable to
+        certain users, you need to be aware of a possible nonoptimal
+        behavior with <command>svn checkout</command>.</para>
+
+      <para>When the client requests a checkout or update over HTTP,
+        it makes a single server request and receives a single (often
+        large) server response.  When the server receives the request,
+        that is the <emphasis>only</emphasis> opportunity Apache has
+        to demand user authentication.  This has some odd side
+        effects.  For example, if a certain subdirectory of the
+        repository is readable only by user Sally, and user Harry
+        checks out a parent directory, his client will respond to the
+        initial authentication challenge as Harry.  As the server
+        generates the large response, there's no way it can resend an
+        authentication challenge when it reaches the special
+        subdirectory; thus the subdirectory is skipped altogether,
+        rather than asking the user to reauthenticate as Sally at the
+        right moment.  In a similar way, if the root of the repository
+        is anonymously world-readable, the entire checkout will be
+        done without authentication—again, skipping the
+        unreadable directory, rather than asking for authentication
+        partway through.</para>
+    </sidebar>

    </sect1>





More information about the svnbook-dev mailing list