[svnbook] r5821 committed - branches/1.8/zh/book/ ch06-server-configuration.xml
wuzhouhui at users.sourceforge.net
wuzhouhui at users.sourceforge.net
Tue Nov 6 08:49:59 CST 2018
Revision: 5821
http://sourceforge.net/p/svnbook/source/5821
Author: wuzhouhui
Date: 2018-11-06 14:49:57 +0000 (Tue, 06 Nov 2018)
Log Message:
-----------
1.8/zh: translation of chapter 6 in progress
Modified Paths:
--------------
branches/1.8/zh/book/ch06-server-configuration.xml
Modified: branches/1.8/zh/book/ch06-server-configuration.xml
===================================================================
--- branches/1.8/zh/book/ch06-server-configuration.xml 2018-11-04 01:35:19 UTC (rev 5820)
+++ branches/1.8/zh/book/ch06-server-configuration.xml 2018-11-06 14:49:57 UTC (rev 5821)
@@ -7900,11 +7900,19 @@
-->
<title>访问权限控制的一些陷阱</title>
+ <!--
<para>If you're using Apache as your Subversion server and have
made certain subdirectories of your repository unreadable to
+ ### TODO
certain users, you need to be aware of a possible nonoptimal
behavior with <command>svn checkout</command>.</para>
+ -->
+ <para>如果你使用 Apache 作为 Subversion 服务器, 而且还设置了仓库的
+ 某些子目录对某些用户是不可读的, 那么在执行
+ <command>svn checkout</command> 时, 你需要意识到可能会出现的低效
+ 行为.</para>
+ <!--
<para>Depending on which HTTP communication library the
Subversion client is using, it may request that the entire
payload of a checkout or update be delivered in a single
@@ -7921,6 +7929,16 @@
subdirectory; thus the subdirectory is skipped altogether,
rather than asking the user to reauthenticate as Sally at the
right moment.</para>
+ -->
+ <para>取决于 Subversion 客户端所使用的 HTTP 函数库, 它可能会要求检出或
+ 更新的全部载荷在一个单独的响应中递送, 当这种情况发生时, 一开始的认证
+ 请求就是 Apache 向用户要求认证的 <emphasis>唯一</emphasis> 机会,
+ 这会产生一些很奇怪的副作用. 比如说, 如果仓库的某个子目录只有 Sally
+ 具有读权限, 而 Harry 检出了该目录的父目录, 他的客户端将以 Harry 的身
+ 份完成最初的认证. 随着服务器向客户端发送大块的响应数据, 当发送 Harry
+ 不具有读权限的那个子目录时, 服务器再也没有办法再次发送认证请求, 于是
+ 该子目录被忽略, 而用户却无法通过重新以 Sally 的身份进行认证来避免这
+ 种情况.</para>
<para>In a similar way, if the root of the repository is
anonymously world-readable, the entire checkout will be done
More information about the svnbook-dev
mailing list