httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From n.@apache.org
Subject svn commit: r1564960 [11/12] - in /httpd/httpd/trunk/docs/manual: ./ developer/ howto/ misc/ mod/ platform/ programs/ rewrite/ ssl/ vhosts/
Date Wed, 05 Feb 2014 22:28:36 GMT
Modified: httpd/httpd/trunk/docs/manual/mod/mod_vhost_alias.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_vhost_alias.html.en?rev=1564960&r1=1564959&r2=1564960&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_vhost_alias.html.en (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_vhost_alias.html.en Wed Feb  5 22:28:30 2014
@@ -48,10 +48,8 @@ hosting</td></tr>
       /cgi-bin/script.pl</code> to <code>
       /usr/local/apache2/cgi-bin/script.pl</code> in all cases:</p>
 
-      <pre class="prettyprint lang-config">
-ScriptAlias /cgi-bin/ /usr/local/apache2/cgi-bin/
-VirtualScriptAlias /never/found/%0/cgi-bin/
-      </pre>
+      <pre class="prettyprint lang-config">ScriptAlias /cgi-bin/ /usr/local/apache2/cgi-bin/
+VirtualScriptAlias /never/found/%0/cgi-bin/</pre>
 
     </div>
 </div>
@@ -144,10 +142,8 @@ VirtualScriptAlias /never/found/%0/cgi-b
     <p>For simple name-based virtual hosts you might use the
     following directives in your server configuration file:</p>
 
-    <pre class="prettyprint lang-config">
-UseCanonicalName    Off
-VirtualDocumentRoot /usr/local/apache/vhosts/%0
-    </pre>
+    <pre class="prettyprint lang-config">UseCanonicalName    Off
+VirtualDocumentRoot /usr/local/apache/vhosts/%0</pre>
 
 
     <p>A request for
@@ -161,10 +157,8 @@ VirtualDocumentRoot /usr/local/apache/vh
     <code>vhosts</code> directory. To do this you might use the
     following in your configuration file:</p>
 
-    <pre class="prettyprint lang-config">
-UseCanonicalName    Off
-VirtualDocumentRoot /usr/local/apache/vhosts/%3+/%2.1/%2.2/%2.3/%2
-    </pre>
+    <pre class="prettyprint lang-config">UseCanonicalName    Off
+VirtualDocumentRoot /usr/local/apache/vhosts/%3+/%2.1/%2.2/%2.3/%2</pre>
 
 
     <p>A request for
@@ -175,9 +169,7 @@ VirtualDocumentRoot /usr/local/apache/vh
     <p>A more even spread of files can be achieved by hashing from the
     end of the name, for example: </p>
 
-<pre class="prettyprint lang-config">
-    VirtualDocumentRoot /usr/local/apache/vhosts/%3+/%2.-1/%2.-2/%2.-3/%2
-</pre>
+<pre class="prettyprint lang-config">    VirtualDocumentRoot /usr/local/apache/vhosts/%3+/%2.-1/%2.-2/%2.-3/%2</pre>
 
 
     <p>The example request would come from
@@ -185,9 +177,7 @@ VirtualDocumentRoot /usr/local/apache/vh
 
     <p>Alternatively you might use: </p>
 
-<pre class="prettyprint lang-config">
-    VirtualDocumentRoot /usr/local/apache/vhosts/%3+/%2.1/%2.2/%2.3/%2.4+
-</pre>
+<pre class="prettyprint lang-config">    VirtualDocumentRoot /usr/local/apache/vhosts/%3+/%2.1/%2.2/%2.3/%2.4+</pre>
 
 
     <p>The example request would come from
@@ -204,9 +194,7 @@ tld, for example <code>example.com</code
 to the hostname. As such, one can make a configuration that will direct all first, second 
 or third level subdomains to the same directory:
 </p>
-<pre class="prettyprint lang-config">
-    VirtualDocumentRoot "/usr/local/apache/vhosts/%-2.0.%-1.0"
-</pre>
+<pre class="prettyprint lang-config">    VirtualDocumentRoot "/usr/local/apache/vhosts/%-2.0.%-1.0"</pre>
 
 <p>
 In the example above, both <code>www.example.com</code> as well as <code>www.sub.example.com</code>
@@ -216,11 +204,9 @@ or <code>example.com</code> will all poi
     <p>For IP-based virtual hosting you might use the following in
     your configuration file:</p>
 
-    <pre class="prettyprint lang-config">
-UseCanonicalName DNS
+    <pre class="prettyprint lang-config">UseCanonicalName DNS
 VirtualDocumentRootIP /usr/local/apache/vhosts/%1/%2/%3/%4/docs
-VirtualScriptAliasIP  /usr/local/apache/vhosts/%1/%2/%3/%4/cgi-bin
-    </pre>
+VirtualScriptAliasIP  /usr/local/apache/vhosts/%1/%2/%3/%4/cgi-bin</pre>
 
 
     <p>A request for
@@ -238,9 +224,7 @@ VirtualScriptAliasIP  /usr/local/apache/
     a <code>%</code> directive, you can work around the problem in
     the following way:</p>
 
-<pre class="prettyprint lang-config">
-    VirtualDocumentRoot /usr/local/apache/vhosts/%2.0.%3.0
-</pre>
+<pre class="prettyprint lang-config">    VirtualDocumentRoot /usr/local/apache/vhosts/%2.0.%3.0</pre>
 
 
     <p>A request for

Modified: httpd/httpd/trunk/docs/manual/mod/mpm_common.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mpm_common.html.en?rev=1564960&r1=1564959&r2=1564960&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mpm_common.html.en (original)
+++ httpd/httpd/trunk/docs/manual/mod/mpm_common.html.en Wed Feb  5 22:28:30 2014
@@ -178,27 +178,21 @@ listens to</td></tr>
     <p>For example, to make the server accept connections on both
     port 80 and port 8000, use:</p>
 
-    <pre class="prettyprint lang-config">
-Listen 80
-Listen 8000
-    </pre>
+    <pre class="prettyprint lang-config">Listen 80
+Listen 8000</pre>
 
 
     <p>To make the server accept connections on two specified
     interfaces and port numbers, use </p>
 
-    <pre class="prettyprint lang-config">
-Listen 192.170.2.1:80
-Listen 192.170.2.5:8000
-    </pre>
+    <pre class="prettyprint lang-config">Listen 192.170.2.1:80
+Listen 192.170.2.5:8000</pre>
 
 
     <p>IPv6 addresses must be surrounded in square brackets, as in the
     following example:</p>
 
-    <pre class="prettyprint lang-config">
-      Listen [2001:db8::a00:20ff:fea7:ccea]:80
-    </pre>
+    <pre class="prettyprint lang-config">      Listen [2001:db8::a00:20ff:fea7:ccea]:80</pre>
 
 
     <p>The optional <var>protocol</var> argument is not required for most
@@ -211,9 +205,7 @@ Listen 192.170.2.5:8000
     <p>You only need to set the protocol if you are running on non-standard
        ports.  For example, running an <code>https</code> site on port 8443:</p>
 
-    <pre class="prettyprint lang-config">
-      Listen 192.170.2.1:8443 https
-    </pre>
+    <pre class="prettyprint lang-config">      Listen 192.170.2.1:8443 https</pre>
 
 
     <div class="note"><h3>Error condition</h3>
@@ -436,9 +428,7 @@ of the daemon</td></tr>
     filename is not absolute then it is assumed to be relative to the
     <code class="directive"><a href="../mod/core.html#defaultruntimedir">DefaultRuntimeDir</a></code>.</p>
 
-    <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">
-      PidFile /var/run/apache.pid
-      </pre>
+    <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">      PidFile /var/run/apache.pid</pre>
 </div>
 
     <p>It is often useful to be able to send the server a signal,
@@ -496,9 +486,7 @@ the child processes</td></tr>
     will be relative to the value of 
     <code class="directive"><a href="../mod/core.html#defaultruntimedir">DefaultRuntimeDir</a></code>.</p>
 
-    <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">
-      ScoreBoardFile /var/run/apache_runtime_status
-      </pre>
+    <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">      ScoreBoardFile /var/run/apache_runtime_status</pre>
 </div>
 
     <p>File-based shared memory is useful for third-party applications

Modified: httpd/httpd/trunk/docs/manual/mod/worker.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/worker.html.en?rev=1564960&r1=1564959&r2=1564960&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/worker.html.en (original)
+++ httpd/httpd/trunk/docs/manual/mod/worker.html.en Wed Feb  5 22:28:30 2014
@@ -142,14 +142,12 @@
     <p>A typical configuration of the process-thread controls in
     the <code class="module"><a href="../mod/worker.html">worker</a></code> MPM could look as follows:</p>
 
-    <pre class="prettyprint lang-config">
-ServerLimit         16
+    <pre class="prettyprint lang-config">ServerLimit         16
 StartServers         2
 MaxRequestWorkers  150
 MinSpareThreads     25
 MaxSpareThreads     75
-ThreadsPerChild     25
-    </pre>
+ThreadsPerChild     25</pre>
 
 
     <p>While the parent process is usually started as <code>root</code>

Modified: httpd/httpd/trunk/docs/manual/platform/perf-hp.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/platform/perf-hp.html.en?rev=1564960&r1=1564959&r2=1564960&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/platform/perf-hp.html.en (original)
+++ httpd/httpd/trunk/docs/manual/platform/perf-hp.html.en Wed Feb  5 22:28:30 2014
@@ -26,13 +26,11 @@
 </div>
 
 
-<pre>
-Date: Wed, 05 Nov 1997 16:59:34 -0800
+<pre>Date: Wed, 05 Nov 1997 16:59:34 -0800
 From: Rick Jones &lt;<a href="mailto:raj@cup.hp.com">raj@cup.hp.com</a>&gt;
 Reply-To: <a href="mailto:raj@cup.hp.com">raj@cup.hp.com</a>
 Organization: Network Performance
-Subject: HP-UX tuning tips
-</pre>
+Subject: HP-UX tuning tips</pre>
 
     <p>Here are some tuning tips for HP-UX to add to the tuning page.</p>
 

Modified: httpd/httpd/trunk/docs/manual/platform/perf-hp.html.ko.euc-kr
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/platform/perf-hp.html.ko.euc-kr?rev=1564960&r1=1564959&r2=1564960&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/platform/perf-hp.html.ko.euc-kr [euc-kr] (original)
+++ httpd/httpd/trunk/docs/manual/platform/perf-hp.html.ko.euc-kr [euc-kr] Wed Feb  5 22:28:30 2014
@@ -28,13 +28,11 @@
             최근에 변경된 내용은 영어 문서를 참고하세요.</div>
 
 
-<pre>
-Date: Wed, 05 Nov 1997 16:59:34 -0800
+<pre>Date: Wed, 05 Nov 1997 16:59:34 -0800
 From: Rick Jones &lt;<a href="mailto:raj@cup.hp.com">raj@cup.hp.com</a>&gt;
 Reply-To: <a href="mailto:raj@cup.hp.com">raj@cup.hp.com</a>
 Organization: Network Performance
-Subject: HP-UX tuning tips
-</pre>
+Subject: HP-UX tuning tips</pre>
 
     <p>이 글은 성능향상 페이지에 추가할 HP-UX 성능향상 팁이다.</p>
 

Modified: httpd/httpd/trunk/docs/manual/platform/win_compiling.html.ko.euc-kr
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/platform/win_compiling.html.ko.euc-kr?rev=1564960&r1=1564959&r2=1564960&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/platform/win_compiling.html.ko.euc-kr [euc-kr] (original)
+++ httpd/httpd/trunk/docs/manual/platform/win_compiling.html.ko.euc-kr [euc-kr] Wed Feb  5 22:28:30 2014
@@ -179,11 +179,9 @@
     있다. Windows NT에서 <code>release</code>와 <code>debug</code>
     컴파일하는 명령어는 각각 다음과 같다:</p>
 
-    <div class="example"><pre>
-nmake /f Makefile.win _apacher
+    <div class="example"><pre>nmake /f Makefile.win _apacher
 
-nmake /f Makefile.win _apached
-    </pre></div>
+nmake /f Makefile.win _apached</pre></div>
 
     <p>두 명령어 모두 아파치를 컴파일한다. 후자는 결과파일에
     디버깅 정보를 포함하여 버그를 찾고 문제를 추적하기 쉽게
@@ -323,8 +321,7 @@ nmake /f Makefile.win _apached
     <p>컴파일하고 모든 파일을 원하는 폴더 <em>dir</em>에 자동으로
     설치하려면 다음 <code>nmake</code> 명령어중 하나를 사용한다:</p>
 
-    <div class="example"><pre>
-nmake /f Makefile.win installr INSTDIR=<em>dir</em>
+    <div class="example"><pre>nmake /f Makefile.win installr INSTDIR=<em>dir</em>
 
 nmake /f Makefile.win installd INSTDIR=<em>dir</em>
     </pre></div>

Modified: httpd/httpd/trunk/docs/manual/platform/windows.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/platform/windows.html.en?rev=1564960&r1=1564959&r2=1564960&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/platform/windows.html.en (original)
+++ httpd/httpd/trunk/docs/manual/platform/windows.html.en Wed Feb  5 22:28:30 2014
@@ -140,12 +140,10 @@
       how it is accessed.  If you wish to assure that only lowercase
       is used in URLs, you can use something like:</p>
 
-      <pre class="prettyprint lang-config">
-RewriteEngine On
+      <pre class="prettyprint lang-config">RewriteEngine On
 RewriteMap lowercase int:tolower
 RewriteCond %{REQUEST_URI} [A-Z]
-RewriteRule (.*) ${lowercase:$1} [R,L]
-      </pre>
+RewriteRule (.*) ${lowercase:$1} [R,L]</pre>
 </li>
 
       <li><p>When running, Apache needs write access only to the logs
@@ -167,9 +165,7 @@ RewriteRule (.*) ${lowercase:$1} [R,L]
       module, use the following (in addition to the status-activating
       directives in <code>access.conf</code>):</p>
 
-      <pre class="prettyprint lang-config">
-        LoadModule status_module modules/mod_status.so
-      </pre>
+      <pre class="prettyprint lang-config">        LoadModule status_module modules/mod_status.so</pre>
 
 
       <p>Information on <a href="../mod/mod_so.html#creating">creating
@@ -607,23 +603,17 @@ RewriteRule (.*) ${lowercase:$1} [R,L]
   (Arcane and error prone procedures may work around the restriction
   on mapped drive letters, but this is not recommended.)</p>
 
-  <div class="example"><h3>Example DocumentRoot with UNC path</h3><pre class="prettyprint lang-config">
-  DocumentRoot //dochost/www/html/
-  </pre>
+  <div class="example"><h3>Example DocumentRoot with UNC path</h3><pre class="prettyprint lang-config">  DocumentRoot //dochost/www/html/</pre>
 </div>
 
-  <div class="example"><h3>Example DocumentRoot with IP address in UNC path</h3><pre class="prettyprint lang-config">
-  DocumentRoot //192.168.1.50/docs/
-  </pre>
+  <div class="example"><h3>Example DocumentRoot with IP address in UNC path</h3><pre class="prettyprint lang-config">  DocumentRoot //192.168.1.50/docs/</pre>
 </div>
 
-  <div class="example"><h3>Example Alias and corresponding Directory with UNC path</h3><pre class="prettyprint lang-config">
-Alias /images/ //imagehost/www/images/
+  <div class="example"><h3>Example Alias and corresponding Directory with UNC path</h3><pre class="prettyprint lang-config">Alias /images/ //imagehost/www/images/
 
 &lt;Directory //imagehost/www/images/&gt;
 #...
-&lt;Directory&gt;
-  </pre>
+&lt;Directory&gt;</pre>
 </div>
 
   <p>When running Apache httpd as a service, you must create a

Modified: httpd/httpd/trunk/docs/manual/programs/log_server_status.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/programs/log_server_status.html.en?rev=1564960&r1=1564959&r2=1564960&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/programs/log_server_status.html.en (original)
+++ httpd/httpd/trunk/docs/manual/programs/log_server_status.html.en Wed Feb  5 22:28:30 2014
@@ -38,12 +38,10 @@
 
 <p>The script contains the following section.</p>
 
-<pre class="prettyprint lang-perl">
-my $wherelog = "/usr/local/apache2/logs/";  # Logs will be like "/usr/local/apache2/logs/19960312"
+<pre class="prettyprint lang-perl">my $wherelog = "/usr/local/apache2/logs/";  # Logs will be like "/usr/local/apache2/logs/19960312"
 my $server   = "localhost";        # Name of server, could be "www.foo.com"
 my $port     = "80";               # Port on server
-my $request = "/server-status/?auto";    # Request to send
-</pre>
+my $request = "/server-status/?auto";    # Request to send</pre>
 
 
 <p>You'll need to ensure that these variables have the correct values,

Modified: httpd/httpd/trunk/docs/manual/programs/split-logfile.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/programs/split-logfile.html.en?rev=1564960&r1=1564959&r2=1564960&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/programs/split-logfile.html.en (original)
+++ httpd/httpd/trunk/docs/manual/programs/split-logfile.html.en Wed Feb  5 22:28:30 2014
@@ -36,10 +36,8 @@
 
     <p>Create a log file with virtual host information in it:</p>
 
-    <pre class="prettyprint lang-config">
-LogFormat "%v %h %l %u %t \"%r\" %&gt;s %b \"%{Referer}i\" \"%{User-agent}i\"" combined_plus_vhost
-CustomLog logs/access_log combined_plus_vhost
-    </pre>
+    <pre class="prettyprint lang-config">LogFormat "%v %h %l %u %t \"%r\" %&gt;s %b \"%{Referer}i\" \"%{User-agent}i\"" combined_plus_vhost
+CustomLog logs/access_log combined_plus_vhost</pre>
 
 
     <p>Log files will be created, in the directory where you run the

Modified: httpd/httpd/trunk/docs/manual/rewrite/access.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/rewrite/access.html.en?rev=1564960&r1=1564959&r2=1564960&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/rewrite/access.html.en (original)
+++ httpd/httpd/trunk/docs/manual/rewrite/access.html.en Wed Feb  5 22:28:30 2014
@@ -78,31 +78,25 @@ configuration.</div>
 
 
 
-<pre class="prettyprint lang-config">
-RewriteCond %{HTTP_REFERER} !^$
+<pre class="prettyprint lang-config">RewriteCond %{HTTP_REFERER} !^$
 RewriteCond %{HTTP_REFERER} !www.example.com [NC]
-RewriteRule \.(gif|jpg|png)$    -   [F,NC]
-</pre>
+RewriteRule \.(gif|jpg|png)$    -   [F,NC]</pre>
 
 
     <p>In this second example, instead of failing the request, we display
     an alternate image instead.</p>
 
-<pre class="prettyprint lang-config">
-RewriteCond %{HTTP_REFERER} !^$
+<pre class="prettyprint lang-config">RewriteCond %{HTTP_REFERER} !^$
 RewriteCond %{HTTP_REFERER} !www.example.com [NC]
-RewriteRule \.(gif|jpg|png)$    /images/go-away.png   [R,NC]
-</pre>
+RewriteRule \.(gif|jpg|png)$    /images/go-away.png   [R,NC]</pre>
 
 
     <p>In the third example, we redirect the request to an image on some
     other site.</p>
 
-<pre class="prettyprint lang-config">
-RewriteCond %{HTTP_REFERER} !^$
+<pre class="prettyprint lang-config">RewriteCond %{HTTP_REFERER} !^$
 RewriteCond %{HTTP_REFERER} !www.example.com [NC]
-RewriteRule \.(gif|jpg|png)$ http://other.example.com/image.gif   [R,NC]
-</pre>
+RewriteRule \.(gif|jpg|png)$ http://other.example.com/image.gif   [R,NC]</pre>
 
 
     <p>Of these techniques, the last two tend to be the most effective
@@ -118,12 +112,10 @@ RewriteRule \.(gif|jpg|png)$ http://othe
         than redirecting that request elsewhere, this can be
         accomplished without the use of mod_rewrite:</p>
 
-        <pre class="prettyprint lang-config">
-SetEnvIf Referer example\.com localreferer
+        <pre class="prettyprint lang-config">SetEnvIf Referer example\.com localreferer
 &lt;FilesMatch \.(jpg|png|gif)$&gt;
     Require env localreferer
-&lt;/FilesMatch&gt;
-        </pre>
+&lt;/FilesMatch&gt;</pre>
 
         </dd>
       </dl>
@@ -167,11 +159,9 @@ SetEnvIf Referer example\.com localrefer
         range, if you are trying to block that user agent only from the
         particular source.</p>
 
-<pre class="prettyprint lang-config">
-RewriteCond %{HTTP_USER_AGENT}   ^NameOfBadRobot
+<pre class="prettyprint lang-config">RewriteCond %{HTTP_USER_AGENT}   ^NameOfBadRobot
 RewriteCond %{REMOTE_ADDR}       =123\.45\.67\.[8-9]
-RewriteRule ^/secret/files/   -   [F]
-</pre>
+RewriteRule ^/secret/files/   -   [F]</pre>
 
         </dd>
 
@@ -182,15 +172,13 @@ RewriteRule ^/secret/files/   -   [F]
         Rather than using mod_rewrite for this, you can accomplish the
         same end using alternate means, as illustrated here:
       </p>
-      <pre class="prettyprint lang-config">
-SetEnvIfNoCase User-Agent ^NameOfBadRobot goaway
+      <pre class="prettyprint lang-config">SetEnvIfNoCase User-Agent ^NameOfBadRobot goaway
 &lt;Location /secret/files&gt;
     &lt;RequireAll&gt;
         Require all granted
         Require not env goaway
     &lt;/RequireAll&gt;
-&lt;/Location&gt;
-      </pre>
+&lt;/Location&gt;</pre>
 
       <p>
       As noted above, this technique is trivial to circumvent, by simply
@@ -221,13 +209,11 @@ SetEnvIfNoCase User-Agent ^NameOfBadRobo
     <dt>Solution:</dt>
 
     <dd>
-<pre class="prettyprint lang-config">
-RewriteEngine on
+<pre class="prettyprint lang-config">RewriteEngine on
 RewriteMap    hosts-deny  txt:/path/to/hosts.deny
 RewriteCond   ${hosts-deny:%{REMOTE_ADDR}|NOT-FOUND} !=NOT-FOUND [OR]
 RewriteCond   ${hosts-deny:%{REMOTE_HOST}|NOT-FOUND} !=NOT-FOUND
-RewriteRule   ^  -  [F]
-</pre>
+RewriteRule   ^  -  [F]</pre>
 
 
 <div class="example"><p><code>
@@ -276,8 +262,7 @@ bsdti1.sdm.de  -<br />
   <p>The following ruleset uses a map file to associate each Referer
   with a redirection target.</p>
 
-<pre class="prettyprint lang-config">
-RewriteMap  deflector txt:/path/to/deflector.map
+<pre class="prettyprint lang-config">RewriteMap  deflector txt:/path/to/deflector.map
 
 RewriteCond %{HTTP_REFERER} !=""
 RewriteCond ${deflector:%{HTTP_REFERER}} =-
@@ -285,23 +270,20 @@ RewriteRule ^ %{HTTP_REFERER} [R,L]
 
 RewriteCond %{HTTP_REFERER} !=""
 RewriteCond ${deflector:%{HTTP_REFERER}|NOT-FOUND} !=NOT-FOUND
-RewriteRule ^ ${deflector:%{HTTP_REFERER}} [R,L]
-</pre>
+RewriteRule ^ ${deflector:%{HTTP_REFERER}} [R,L]</pre>
 
 
       <p>The map file lists redirection targets for each referer, or, if
       we just wish to redirect back to where they came from, a "-" is
       placed in the map:</p>
 
-<pre class="prettyprint lang-config">
-##<br />
+<pre class="prettyprint lang-config">##<br />
 ##  deflector.map<br />
 ##<br />
 <br />
 http://badguys.example.com/bad/index.html    -<br />
 http://badguys.example.com/bad/index2.html   -<br />
-http://badguys.example.com/bad/index3.html   http://somewhere.example.com/
-</pre>
+http://badguys.example.com/bad/index3.html   http://somewhere.example.com/</pre>
 
 
     </dd>

Modified: httpd/httpd/trunk/docs/manual/rewrite/advanced.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/rewrite/advanced.html.en?rev=1564960&r1=1564959&r2=1564960&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/rewrite/advanced.html.en (original)
+++ httpd/httpd/trunk/docs/manual/rewrite/advanced.html.en Wed Feb  5 22:28:30 2014
@@ -91,11 +91,9 @@ http://physical_host_of_user1/u/user/any
       files assuming that server0 is a default server which will be used if
       a user has no entry in the map:</p>
 
-<pre class="prettyprint lang-config">
-RewriteEngine on
+<pre class="prettyprint lang-config">RewriteEngine on
 RewriteMap      users-to-hosts   txt:/path/to/map.users-to-hosts
-RewriteRule   ^/u/([^/]+)/?(.*)   http://${users-to-hosts:$1|server0}/u/$1/$2
-</pre>
+RewriteRule   ^/u/([^/]+)/?(.*)   http://${users-to-hosts:$1|server0}/u/$1/$2</pre>
 
     </dd>
   </dl>
@@ -125,11 +123,9 @@ RewriteRule   ^/u/([^/]+)/?(.*)   http:/
     <dd>
       This is done via the following ruleset:
 
-<pre class="prettyprint lang-config">
-# This example is valid in per-directory context only
+<pre class="prettyprint lang-config"># This example is valid in per-directory context only
 RewriteCond %{REQUEST_URI}   !-U
-RewriteRule ^(.+)\.html$          /regenerate_page.cgi   [PT,L]
-</pre>
+RewriteRule ^(.+)\.html$          /regenerate_page.cgi   [PT,L]</pre>
 
 
     <p>The <code>-U</code> operator determines whether the test string
@@ -167,11 +163,9 @@ RewriteRule ^(.+)\.html$          /regen
       <p>We'll use <code class="directive"><a href="../mod/mod_rewrite.html#rewritemap">RewriteMap</a></code> and a list of servers
       to accomplish this.</p>
 
-<pre class="prettyprint lang-config">
-RewriteEngine on
+<pre class="prettyprint lang-config">RewriteEngine on
 RewriteMap lb rnd:/path/to/serverlist.txt
-RewriteRule ^/(.*) http://${lb:servers}/$1 [P,L]
-</pre>
+RewriteRule ^/(.*) http://${lb:servers}/$1 [P,L]</pre>
 
 
 <p><code>serverlist.txt</code> will contain a list of the servers:</p>
@@ -223,9 +217,7 @@ featureful than anything you can cobble 
       URL causes the 'page' to be refreshed every time it is
       updated on the filesystem.</p>
 
-<pre class="prettyprint lang-config">
-RewriteRule   ^(/[uge]/[^/]+/?.*):refresh  /internal/cgi/apache/nph-refresh?f=$1
-</pre>
+<pre class="prettyprint lang-config">RewriteRule   ^(/[uge]/[^/]+/?.*):refresh  /internal/cgi/apache/nph-refresh?f=$1</pre>
 
 
       <p>Now when we reference the URL</p>
@@ -244,8 +236,7 @@ RewriteRule   ^(/[uge]/[^/]+/?.*):refres
       one would usually say "left as an exercise to the reader"
       ;-) I will provide this, too.</p>
 
-<pre class="prettyprint lang-perl">
-#!/sw/bin/perl
+<pre class="prettyprint lang-perl">#!/sw/bin/perl
 ##
 ##  nph-refresh -- NPH/CGI script for auto refreshing pages
 ##  Copyright (c) 1997 Ralf S. Engelschall, All Rights Reserved.
@@ -345,8 +336,7 @@ for ( $n = 0 ; $n &amp; lt ; $QS_n ; $n+
 
 exit(0);
 
-##EOF##
-</pre>
+##EOF##</pre>
 
     </dd>
   </dl>
@@ -376,10 +366,8 @@ exit(0);
       <p>We use the following ruleset to expand the tilde URLs
       into the above layout.</p>
 
-<pre class="prettyprint lang-config">
-RewriteEngine on
-RewriteRule   ^/~(<strong>([a-z])</strong>[a-z0-9]+)(.*)  /home/<strong>$2</strong>/$1/public_html$3
-</pre>
+<pre class="prettyprint lang-config">RewriteEngine on
+RewriteRule   ^/~(<strong>([a-z])</strong>[a-z0-9]+)(.*)  /home/<strong>$2</strong>/$1/public_html$3</pre>
 
     </dd>
   </dl>
@@ -436,13 +424,11 @@ RewriteRule   ^/~(<strong>([a-z])</stron
       <code>&gt;STRING</code> and <code>=STRING</code> we can
       do time-dependent redirects:</p>
 
-<pre class="prettyprint lang-config">
-RewriteEngine on
+<pre class="prettyprint lang-config">RewriteEngine on
 RewriteCond   %{TIME_HOUR}%{TIME_MIN} &gt;0700
 RewriteCond   %{TIME_HOUR}%{TIME_MIN} &lt;1900
 RewriteRule   ^foo\.html$             foo.day.html [L]
-RewriteRule   ^foo\.html$             foo.night.html
-</pre>
+RewriteRule   ^foo\.html$             foo.night.html</pre>
 
 
       <p>This provides the content of <code>foo.day.html</code>
@@ -482,18 +468,14 @@ RewriteRule   ^foo\.html$             fo
     <dd>
       <p>Use the [E] flag to set an environment variable.</p>
 
-<pre class="prettyprint lang-config">
-RewriteEngine on
-RewriteRule   ^/horse/(.*)   /pony/$1 [E=<strong>rewritten:1</strong>]
-</pre>
+<pre class="prettyprint lang-config">RewriteEngine on
+RewriteRule   ^/horse/(.*)   /pony/$1 [E=<strong>rewritten:1</strong>]</pre>
 
 
     <p>Later in your ruleset you might check for this environment
     variable using a RewriteCond:</p>
 
-<pre class="prettyprint lang-config">
-RewriteCond %{ENV:rewritten} =1
-</pre>
+<pre class="prettyprint lang-config">RewriteCond %{ENV:rewritten} =1</pre>
 
 
     <p>Note that environment variables do not survive an external

Modified: httpd/httpd/trunk/docs/manual/rewrite/avoid.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/rewrite/avoid.html.en?rev=1564960&r1=1564959&r2=1564960&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/rewrite/avoid.html.en (original)
+++ httpd/httpd/trunk/docs/manual/rewrite/avoid.html.en Wed Feb  5 22:28:30 2014
@@ -89,8 +89,7 @@ and <code>/one/three/four.html</code>.</
 <p>To redirect <code>http</code> URLs to <code>https</code>, do the
 following:</p>
 
-<pre class="prettyprint lang-config">
-&lt;VirtualHost *:80&gt;
+<pre class="prettyprint lang-config">&lt;VirtualHost *:80&gt;
     ServerName www.example.com
     Redirect / https://www.example.com/
 &lt;/VirtualHost &gt;
@@ -98,8 +97,7 @@ following:</p>
 &lt;VirtualHost *:443&gt;
     ServerName www.example.com
     # ... SSL configuration goes here
-&lt;/VirtualHost &gt;
-</pre>
+&lt;/VirtualHost &gt;</pre>
 
 
 <p>The use of <code>RewriteRule</code> to perform this task may be
@@ -165,27 +163,21 @@ seems like the right approach.</p>
 <p><code>RewriteRule</code> provides the <a href="flags.html#flag_p">[P]</a> flag to pass rewritten URIs through
 <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code>.</p>
 
-<pre class="prettyprint lang-config">
-RewriteRule ^/?images(.*) http://imageserver.local/images$1 [P]
-</pre>
+<pre class="prettyprint lang-config">RewriteRule ^/?images(.*) http://imageserver.local/images$1 [P]</pre>
 
 
 <p>However, in many cases, when there is no actual pattern matching
 needed, as in the example shown above, the <code class="directive"><a href="../mod/mod_proxy.html#proxypass">ProxyPass</a></code> directive is a better choice.
 The example here could be rendered as:</p>
 
-<pre class="prettyprint lang-config">
-ProxyPass /images/ http://imageserver.local/images/
-</pre>
+<pre class="prettyprint lang-config">ProxyPass /images/ http://imageserver.local/images/</pre>
 
 
 <p>Note that whether you use <code class="directive"><a href="../mod/mod_rewrite.html#rewriterule">RewriteRule</a></code> or <code class="directive"><a href="../mod/mod_proxy.html#proxypass">ProxyPass</a></code>, you'll still need to use the
 <code class="directive"><a href="../mod/mod_proxy.html#proxypassreverse">ProxyPassReverse</a></code> directive to
 catch redirects issued from the back-end server:</p>
 
-<pre class="prettyprint lang-config">
-ProxyPassReverse /images/ http://imageserver.local/images/
-</pre>
+<pre class="prettyprint lang-config">ProxyPassReverse /images/ http://imageserver.local/images/</pre>
 
 
 <p>You may need to use <code>RewriteRule</code> instead when there are
@@ -208,11 +200,9 @@ variable or request header. This can be 
 hostname, such as <code>www.example.com</code> instead of
 <code>example.com</code>. This can be done using the <code class="directive"><a href="../mod/core.html#if">&lt;If&gt;</a></code> directive, as shown here:</p>
 
-<pre class="prettyprint lang-config">
-&lt;If "req('Host') != 'www.example.com'"&gt;
+<pre class="prettyprint lang-config">&lt;If "req('Host') != 'www.example.com'"&gt;
     Redirect / http://www.example.com/
-&lt;/If&gt;
-</pre>
+&lt;/If&gt;</pre>
 
 
 <p>This technique can be used to take actions based on any request

Modified: httpd/httpd/trunk/docs/manual/rewrite/flags.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/rewrite/flags.html.en?rev=1564960&r1=1564959&r2=1564960&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/rewrite/flags.html.en (original)
+++ httpd/httpd/trunk/docs/manual/rewrite/flags.html.en Wed Feb  5 22:28:30 2014
@@ -173,10 +173,8 @@ browsers that support this feature.</dd>
 
 <p>Consider this example:</p>
 
-<pre class="prettyprint lang-config">
-RewriteEngine On
-RewriteRule ^/index\.html - [CO=frontdoor:yes:.example.com:1440:/]
-</pre>
+<pre class="prettyprint lang-config">RewriteEngine On
+RewriteRule ^/index\.html - [CO=frontdoor:yes:.example.com:1440:/]</pre>
 
 
 <p>In the example give, the rule doesn't rewrite the request.
@@ -262,10 +260,8 @@ value of '1' if the requested URI is an 
 environment variable is used to exclude those requests from the access
 log.</p>
 
-<pre class="prettyprint lang-config">
-RewriteRule \.(png|gif|jpg)$ - [E=image:1]
-CustomLog logs/access_log combined env=!image
-</pre>
+<pre class="prettyprint lang-config">RewriteRule \.(png|gif|jpg)$ - [E=image:1]
+CustomLog logs/access_log combined env=!image</pre>
 
 
 <p>Note that this same effect can be obtained using <code class="directive"><a href="../mod/mod_setenvif.html#setenvif">SetEnvIf</a></code>. This technique is offered as
@@ -336,9 +332,7 @@ For example, the following snippet used 
 <code>.php</code> files to be <em>displayed</em> by <code>mod_php</code>
 if they are requested with the <code>.phps</code> extension:</p>
 
-<pre class="prettyprint lang-config">
-RewriteRule ^(/source/.+\.php)s$ $1 [H=application/x-httpd-php-source]
-</pre>
+<pre class="prettyprint lang-config">RewriteRule ^(/source/.+\.php)s$ $1 [H=application/x-httpd-php-source]</pre>
 
 
 <p>The regular expression above - <code>^(/source/.+\.php)s$</code> - will
@@ -386,11 +380,9 @@ redirects.</p>
 argument to <code>index.php</code>, however, the <code class="directive"><a href="../mod/mod_rewrite.html#rewritecond">RewriteCond</a></code> ensures that if the request
 is already for <code>index.php</code>, the <code class="directive"><a href="../mod/mod_rewrite.html#rewriterule">RewriteRule</a></code> will be skipped.</p>
 
-<pre class="prettyprint lang-config">
-RewriteBase /
+<pre class="prettyprint lang-config">RewriteBase /
 RewriteCond %{REQUEST_URI} !=/index.php
-RewriteRule ^(.*) /index.php?req=$1 [L,PT]
-</pre>
+RewriteRule ^(.*) /index.php?req=$1 [L,PT]</pre>
 
 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
 <div class="section">
@@ -416,12 +408,10 @@ pattern still matches (i.e., while the U
 <p>In 2.5.0 and later, this module returns an error after 10,000 iterations to
 protect against unintended looping.  An alternative maximum number of 
 iterations can be specified by adding to the N flag.  </p>
-<pre class="prettyprint lang-config">
-# Be willing to replace 1 character in each pass of the loop
+<pre class="prettyprint lang-config"># Be willing to replace 1 character in each pass of the loop
 RewriteRule (.+)[&gt;&lt;;]$ $1 [N=32000]
 # ... or, give up if after 10 loops
-RewriteRule (.+)[&gt;&lt;;]$ $1 [N=10]
-</pre>
+RewriteRule (.+)[&gt;&lt;;]$ $1 [N=10]</pre>
 
 
 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
@@ -545,10 +535,8 @@ use the [PT] flag to ensure that the
 <code class="directive"><a href="../mod/mod_alias.html#alias">Alias</a></code> is evaluated.
 </p>
 
-<pre class="prettyprint lang-config">
-Alias /icons /usr/local/apache/icons
-RewriteRule /pics/(.+)\.jpg$ /icons/$1.gif [PT]
-</pre>
+<pre class="prettyprint lang-config">Alias /icons /usr/local/apache/icons
+RewriteRule /pics/(.+)\.jpg$ /icons/$1.gif [PT]</pre>
 
 
 <p>
@@ -655,16 +643,14 @@ example, we only want to run the <code c
 RewriteRule</a></code> if the requested URI doesn't correspond with an 
 actual file.</p>
 
-<pre class="prettyprint lang-config">
-# Is the request for a non-existent file?
+<pre class="prettyprint lang-config"># Is the request for a non-existent file?
 RewriteCond %{REQUEST_FILENAME} !-f
 RewriteCond %{REQUEST_FILENAME} !-d
 # If so, skip these two RewriteRules
 RewriteRule .? - [S=2]
 
 RewriteRule (.*\.gif) images.php?$1
-RewriteRule (.*\.html) docs.php?$1
-</pre>
+RewriteRule (.*\.html) docs.php?$1</pre>
 
 
 <p>This technique is useful because a <code class="directive"><a href="../mod/mod_rewrite.html#rewritecond">RewriteCond</a></code> only applies to the
@@ -675,8 +661,7 @@ negate those conditions and add a <code>
 use this to make pseudo if-then-else constructs: The last rule of
 the then-clause becomes <code>skip=N</code>, where N is the
 number of rules in the else-clause:</p>
-<pre class="prettyprint lang-config">
-# Does the file exist?
+<pre class="prettyprint lang-config"># Does the file exist?
 RewriteCond %{REQUEST_FILENAME} !-f
 RewriteCond %{REQUEST_FILENAME} !-d
 # Create an if-then-else construct by skipping 3 lines if we meant to go to the "else" stanza.
@@ -689,8 +674,7 @@ RewriteRule .? - [S=3]
     RewriteRule .? - [S=1]
 # ELSE...
     RewriteRule (.*) 404.php?file=$1
-# END
-</pre>
+# END</pre>
 
 
 <p>It is probably easier to accomplish this kind of configuration using
@@ -705,20 +689,16 @@ sent. This has the same effect as the <c
 <p>For example, you might use the following technique to serve Perl
 source code as plain text, if requested in a particular way:</p>
 
-<pre class="prettyprint lang-config">
-# Serve .pl files as plain text
-RewriteRule \.pl$ - [T=text/plain]
-</pre>
+<pre class="prettyprint lang-config"># Serve .pl files as plain text
+RewriteRule \.pl$ - [T=text/plain]</pre>
 
 
 <p>Or, perhaps, if you have a camera that produces jpeg images without
 file extensions, you could force those images to be served with the
 correct MIME type by virtue of their file names:</p>
 
-<pre class="prettyprint lang-config">
-# Files with 'IMG' in the name are jpg images.
-RewriteRule IMG - [T=image/jpg]
-</pre>
+<pre class="prettyprint lang-config"># Files with 'IMG' in the name are jpg images.
+RewriteRule IMG - [T=image/jpg]</pre>
 
 
 <p>Please note that this is a trivial example, and could be better done

Modified: httpd/httpd/trunk/docs/manual/rewrite/flags.html.fr
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/rewrite/flags.html.fr?rev=1564960&r1=1564959&r2=1564960&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/rewrite/flags.html.fr (original)
+++ httpd/httpd/trunk/docs/manual/rewrite/flags.html.fr Wed Feb  5 22:28:30 2014
@@ -187,10 +187,8 @@ fonctionnalité.</dd>
 
 <p>Voici un exemple :</p>
 
-<pre class="prettyprint lang-config">
-RewriteEngine On
-RewriteRule ^/index\.html - [CO=frontdoor:yes:.example.org:1440:/]
-</pre>
+<pre class="prettyprint lang-config">RewriteEngine On
+RewriteRule ^/index\.html - [CO=frontdoor:yes:.example.org:1440:/]</pre>
 
 
 <p>Dans l'exemple ci-dessus, la règle ne réécrit
@@ -358,9 +356,7 @@ faire en sorte que les fichiers <code>.p
 <em>affichés</em> par <code>mod_php</code> dans le cas où ils font
 l'objet d'une requête avec l'extension <code>.phps</code> :</p>
 
-<pre class="prettyprint lang-config">
-RewriteRule ^(/source/.+\.php)s$ $1 [H=application/x-httpd-php-source]
-</pre>
+<pre class="prettyprint lang-config">RewriteRule ^(/source/.+\.php)s$ $1 [H=application/x-httpd-php-source]</pre>
 
 
 
@@ -414,11 +410,9 @@ de requête en argument à <code>index.p
 directive <code class="directive"><a href="../mod/mod_rewrite.html#rewritecond">RewriteCond</a></code> permet de s'assurer que si
 la requête concerne déjà <code>index.php</code>, la directive <code class="directive"><a href="../mod/mod_rewrite.html#rewriterule">RewriteRule</a></code> sera sautée.</p>
 
-<pre class="prettyprint lang-config">
-RewriteBase /
+<pre class="prettyprint lang-config">RewriteBase /
 RewriteCond %{REQUEST_URI} !=/index.php
-RewriteRule ^(.*) /index.php?req=$1 [L,PT]
-</pre>
+RewriteRule ^(.*) /index.php?req=$1 [L,PT]</pre>
 
 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
 <div class="section">
@@ -448,12 +442,10 @@ un <code>B</code>).</p>
 <p>A partir de la version 2.5.0, ce module renvoie une erreur après
 10000 itérations afin d'éviter les boucles infinies. Ce nombre maximum
 d'itération peut être modifié via le drapeau N.</p>
-<pre class="prettyprint lang-config">
-# On veut remplacer 1 caractère à chaque itération de la boucle
+<pre class="prettyprint lang-config"># On veut remplacer 1 caractère à chaque itération de la boucle
 RewriteRule (.+)[&gt;&lt;;]$ $1 [N=32000]
 # ... ou s'arrêter après 10 itérations
-RewriteRule (.+)[&gt;&lt;;]$ $1 [N=10]
-</pre>
+RewriteRule (.+)[&gt;&lt;;]$ $1 [N=10]</pre>
 
 
 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
@@ -585,10 +577,8 @@ Si par exemple, vous avez un <code class
 vous devez utiliser le drapeau [PT] pour être sûr que l'<code class="directive"><a href="../mod/mod_alias.html#alias">Alias</a></code> sera bien évalué.
 </p>
 
-<pre class="prettyprint lang-config">
-Alias /icons /usr/local/apache/icons
-RewriteRule /pics/(.+)\.jpg$ /icons/$1.gif [PT]
-</pre>
+<pre class="prettyprint lang-config">Alias /icons /usr/local/apache/icons
+RewriteRule /pics/(.+)\.jpg$ /icons/$1.gif [PT]</pre>
 
 
 <p>
@@ -701,16 +691,14 @@ Ceci peut s'interpréter comme une instr
 <code>goto</code>  dans votre jeu de règles de réécriture. Dans
 l'exemple suivant, nous ne voulons exécuter la règle <code class="directive"><a href="../mod/mod_rewrite.html#rewriterule">RewriteRule</a></code> que si l'URI demandé ne
 correspond pas à un fichier existant.</p>
-<pre class="prettyprint lang-config">
-# La requête concerne-t-elle un fichier qui n'existe pas ?
+<pre class="prettyprint lang-config"># La requête concerne-t-elle un fichier qui n'existe pas ?
 RewriteCond %{REQUEST_FILENAME} !-f
 RewriteCond %{REQUEST_FILENAME} !-d
 # Si c'est la cas, on saute les deux règles de réécriture suivantes
 RewriteRule .? - [S=2]
 
 RewriteRule (.*\.gif) images.php?$1
-RewriteRule (.*\.html) docs.php?$1
-</pre>
+RewriteRule (.*\.html) docs.php?$1</pre>
 
 
 
@@ -724,8 +712,7 @@ conditions et ajouter une <code>RewriteR
 d'élaborer des pseudo-constructions if-then-else : la dernière règle du
 bloc then contiendra <code>skip=N</code>, où N est le nombre de règles
 contenues dans le bloc else :</p>
-<pre class="prettyprint lang-config">
-# Est-ce que le fichier existe ?
+<pre class="prettyprint lang-config"># Est-ce que le fichier existe ?
 RewriteCond %{REQUEST_FILENAME} !-f
 RewriteCond %{REQUEST_FILENAME} !-d
 # Create an if-then-else construct by skipping 3 lines if we meant to go to the "else" stanza.
@@ -738,8 +725,7 @@ RewriteRule (.*\.gif) images.php?$1
     RewriteRule .? - [S=1]
 # ELSE...
 RewriteRule (.*) 404.php?file=$1
-# END
-</pre>
+# END</pre>
 
 
 <p>Il est probablement plus aisé de définir ce genre de configuration
@@ -755,20 +741,16 @@ identique à celui de la directive <code
 du code source Perl en tant que plein texte, s'il est requis d'une
 certaine manière :</p>
 
-<pre class="prettyprint lang-config">
-# Sert les fichier .pl en tant que plein texte
-RewriteRule \.pl$ - [T=text/plain]
-</pre>
+<pre class="prettyprint lang-config"># Sert les fichier .pl en tant que plein texte
+RewriteRule \.pl$ - [T=text/plain]</pre>
 
 
 <p>Ou encore, si vous possédez une caméra qui produit des fichiers
 images jpeg sans extension, vous pouvez forcer le renvoi de ces images
 avec le type MIME correct en se basant sur le nom du fichier :</p>
 
-<pre class="prettyprint lang-config">
-# Les fichiers dont le nom contient 'IMG' sont des images jpg.
-RewriteRule IMG - [T=image/jpg]
-</pre>
+<pre class="prettyprint lang-config"># Les fichiers dont le nom contient 'IMG' sont des images jpg.
+RewriteRule IMG - [T=image/jpg]</pre>
 
 
 <p>Notez cependant qu'il s'agit d'un exemple trivial, et que le problème

Modified: httpd/httpd/trunk/docs/manual/rewrite/intro.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/rewrite/intro.html.en?rev=1564960&r1=1564959&r2=1564960&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/rewrite/intro.html.en (original)
+++ httpd/httpd/trunk/docs/manual/rewrite/intro.html.en Wed Feb  5 22:28:30 2014
@@ -189,9 +189,7 @@ value.
 <dl>
 <dt>A full filesystem path to a resource</dt>
 <dd>
-<pre class="prettyprint lang-config">
-RewriteRule ^/games /usr/local/games/web
-</pre>
+<pre class="prettyprint lang-config">RewriteRule ^/games /usr/local/games/web</pre>
 
 <p>This maps a request to an arbitrary location on your filesystem, much
 like the <code class="directive"><a href="../mod/mod_alias.html#alias">Alias</a></code> directive.</p>
@@ -199,9 +197,7 @@ like the <code class="directive"><a href
 
 <dt>A web-path to a resource</dt>
 <dd>
-<pre class="prettyprint lang-config">
-RewriteRule ^/foo$ /bar
-</pre>
+<pre class="prettyprint lang-config">RewriteRule ^/foo$ /bar</pre>
 
 <p>If <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code> is set
 to <code>/usr/local/apache2/htdocs</code>, then this directive would
@@ -211,9 +207,7 @@ path <code>/usr/local/apache2/htdocs/bar
 
 <dt>An absolute URL</dt>
 <dd>
-<pre class="prettyprint lang-config">
-RewriteRule ^/product/view$ http://site2.example.com/seeproduct.html [R]
-</pre>
+<pre class="prettyprint lang-config">RewriteRule ^/product/view$ http://site2.example.com/seeproduct.html [R]</pre>
 
 <p>This tells the client to make a new request for the specified URL.</p>
 </dd>
@@ -222,9 +216,7 @@ RewriteRule ^/product/view$ http://site2
 <p>The <var>Substitution</var> can also
 contain <em>back-references</em> to parts of the incoming URL-path
 matched by the <var>Pattern</var>. Consider the following:</p>
-<pre class="prettyprint lang-config">
-RewriteRule ^/product/(.*)/view$ /var/web/productdb/$1
-</pre>
+<pre class="prettyprint lang-config">RewriteRule ^/product/(.*)/view$ /var/web/productdb/$1</pre>
 
 <p>The variable <code>$1</code> will be replaced with whatever text
 was matched by the expression inside the parenthesis in
@@ -246,9 +238,7 @@ application of one or more flags to the 
 matching behavior of a rule can be made case-insensitive by the
 application of the <code>[NC]</code> flag:
 </p>
-<pre class="prettyprint lang-config">
-RewriteRule ^puppy.html smalldog.html [NC]
-</pre>
+<pre class="prettyprint lang-config">RewriteRule ^puppy.html smalldog.html [NC]</pre>
 
 
 <p>For more details on the available flags, their meanings, and
@@ -273,10 +263,8 @@ argument is a list of flags that modify 
 
 <p>For example, to send all requests from a particular IP range to a
 different server, you could use:</p>
-<pre class="prettyprint lang-config">
-RewriteCond %{REMOTE_ADDR} ^10\.2\.
-RewriteRule (.*) http://intranet.example.com$1
-</pre>
+<pre class="prettyprint lang-config">RewriteCond %{REMOTE_ADDR} ^10\.2\.
+RewriteRule (.*) http://intranet.example.com$1</pre>
 
 
 <p>When more than
@@ -286,11 +274,9 @@ the <code class="directive"><a href="../
 applied. For example, to deny requests that contain the word "hack" in
 their query string, unless they also contain a cookie containing
 the word "go", you could use:</p>
-<pre class="prettyprint lang-config">
-RewriteCond %{QUERY_STRING} hack
+<pre class="prettyprint lang-config">RewriteCond %{QUERY_STRING} hack
 RewriteCond %{HTTP_COOKIE} !go
-RewriteRule . - [F]
-</pre>
+RewriteRule . - [F]</pre>
 
 <p>Notice that the exclamation mark specifies a negative match, so the rule is only applied if the cookie does not contain "go".</p>
 
@@ -301,10 +287,8 @@ the <code class="directive"><a href="../
 variables <code>%1</code>, <code>%2</code>, etc. For example, this
 will direct the request to a different directory depending on the
 hostname used to access the site:</p>
-<pre class="prettyprint lang-config">
-RewriteCond %{HTTP_HOST} (.*)
-RewriteRule ^/(.*) /sites/%1/$1
-</pre>
+<pre class="prettyprint lang-config">RewriteCond %{HTTP_HOST} (.*)
+RewriteRule ^/(.*) /sites/%1/$1</pre>
 
 <p>If the request was for <code>http://example.com/foo/bar</code>,
 then <code>%1</code> would contain <code>example.com</code>

Modified: httpd/httpd/trunk/docs/manual/rewrite/intro.html.fr
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/rewrite/intro.html.fr?rev=1564960&r1=1564959&r2=1564960&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/rewrite/intro.html.fr (original)
+++ httpd/httpd/trunk/docs/manual/rewrite/intro.html.fr Wed Feb  5 22:28:30 2014
@@ -213,9 +213,7 @@ trois types :</p>
 <dl>
 <dt>Un chemin complet du système de fichiers vers une ressource</dt>
 <dd>
-<pre class="prettyprint lang-config">
-RewriteRule ^/jeux /usr/local/jeux/web
-</pre>
+<pre class="prettyprint lang-config">RewriteRule ^/jeux /usr/local/jeux/web</pre>
 
 <p>Ceci peut faire correspondre une requête à toute localisation voulue de
 votre système de fichiers, un peu comme la directive <code class="directive"><a href="../mod/mod_alias.html#alias">Alias</a></code>.</p>
@@ -223,9 +221,7 @@ votre système de fichiers, un peu comme
 
 <dt>Un chemin web vers une ressource</dt>
 <dd>
-<pre class="prettyprint lang-config">
-RewriteRule ^/foo$ /bar
-</pre>
+<pre class="prettyprint lang-config">RewriteRule ^/foo$ /bar</pre>
 
 <p>Si la directive <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code> a
 pour valeur <code>/usr/local/apache2/htdocs</code>, cette règle va faire
@@ -235,9 +231,7 @@ chemin <code>/usr/local/apache2/htdocs/b
 
 <dt>Une URL absolue</dt>
 <dd>
-<pre class="prettyprint lang-config">
-RewriteRule ^/produits/vues$ http://site2.example.com/voirproduits.html [R]
-</pre>
+<pre class="prettyprint lang-config">RewriteRule ^/produits/vues$ http://site2.example.com/voirproduits.html [R]</pre>
 
 <p>Ceci informe le client qu'il doit effectuer une nouvelle requête vers
 l'URL spécifiée.</p>
@@ -247,9 +241,7 @@ l'URL spécifiée.</p>
 <p>La chaîne de <var>Substitution</var> peut aussi contenir des
 <em>références arrières</em> vers des parties du chemin d'URL entrant
 correspondant au <var>Modèle</var>. Considérons ce qui suit :</p>
-<pre class="prettyprint lang-config">
-RewriteRule ^/produits/(.*)/view$ /var/web/produitsdb/$1
-</pre>
+<pre class="prettyprint lang-config">RewriteRule ^/produits/(.*)/view$ /var/web/produitsdb/$1</pre>
 
 <p>La variable <code>$1</code> sera remplacée par tout texte
 correspondant à l'expression située entre les parenthèses dans le
@@ -270,9 +262,7 @@ présence d'un ou plusieurs drapeaux en 
 conditions de correspondance d'une règle peuvent être rendues
 insensibles à la casse par la présence du drapeau <code>[NC]</code> :
 </p>
-<pre class="prettyprint lang-config">
-RewriteRule ^puppy.html petitchien.html [NC]
-</pre>
+<pre class="prettyprint lang-config">RewriteRule ^puppy.html petitchien.html [NC]</pre>
 
 
 <p>Pour une liste des drapeaux disponibles, leurs significations, et des
@@ -299,10 +289,8 @@ correspondance est évaluée.</p>
 <p>Par exemple, pour renvoyer toutes les requêtes en provenance d'une
 certaine tranche d'adresses IP vers un autre serveur, vous pouvez
 utiliser :</p>
-<pre class="prettyprint lang-config">
-RewriteCond %{REMOTE_ADDR} ^10\.2\.
-RewriteRule (.*) http://intranet.example.com$1
-</pre>
+<pre class="prettyprint lang-config">RewriteCond %{REMOTE_ADDR} ^10\.2\.
+RewriteRule (.*) http://intranet.example.com$1</pre>
 
 
 <p>Si vous spécifiez plus d'une directive <code class="directive"><a href="../mod/mod_rewrite.html#rewritecond">RewriteCond</a></code>, ces directives
@@ -310,11 +298,9 @@ doivent toutes être satisfaites pour qu
 pour interdire les requêtes qui contiennent le mot "hack" dans la chaîne
 de requête, sauf si elles contiennent aussi un cookie contenant le mot
 "go", vous pouvez utiliser :</p>
-<pre class="prettyprint lang-config">
-RewriteCond %{QUERY_STRING} hack
+<pre class="prettyprint lang-config">RewriteCond %{QUERY_STRING} hack
 RewriteCond %{HTTP_COOKIE} !go
-RewriteRule . - [F]
-</pre>
+RewriteRule . - [F]</pre>
 
 <p>Notez que le point d'exclamation indique une correspondance négative
 ; ainsi, la règle n'est appliquée que si le cookie ne contient pas "go"</p>
@@ -326,10 +312,8 @@ de la règle <code class="directive"><a 
 les variables <code>%1</code>, <code>%2</code>, etc... Par
 exemple, ce qui suit va diriger la requête vers un répertoire différent
 en fonction du nom d'hôte utilisé pour accéder au site :</p>
-<pre class="prettyprint lang-config">
-RewriteCond %{HTTP_HOST} (.*)
-RewriteRule ^/(.*) /sites/%1/$1
-</pre>
+<pre class="prettyprint lang-config">RewriteCond %{HTTP_HOST} (.*)
+RewriteRule ^/(.*) /sites/%1/$1</pre>
 
 <p>Si la requête concernait <code>http://example.com/foo/bar</code>,
 alors <code>%1</code> contiendrait <code>example.com</code> et

Modified: httpd/httpd/trunk/docs/manual/rewrite/proxy.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/rewrite/proxy.html.en?rev=1564960&r1=1564959&r2=1564960&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/rewrite/proxy.html.en (original)
+++ httpd/httpd/trunk/docs/manual/rewrite/proxy.html.en Wed Feb  5 22:28:30 2014
@@ -56,12 +56,10 @@ A number of recipes are provided that de
       <p>To simply map a URL to another server, we use the [P] flag, as
       follows:</p>
 
-<pre class="prettyprint lang-config">
-RewriteEngine  on
+<pre class="prettyprint lang-config">RewriteEngine  on
 RewriteBase    /products/
 RewriteRule    ^widget/(.*)$  http://product.example.com/widget/$1  [P]
-ProxyPassReverse /products/widget/ http://product.example.com/widget/
-</pre>
+ProxyPassReverse /products/widget/ http://product.example.com/widget/</pre>
 
 
    <p>In the second example, we proxy the request only if we can't find
@@ -69,12 +67,10 @@ ProxyPassReverse /products/widget/ http:
    from one server to another, and you're not sure if all the content
    has been migrated yet.</p>
 
-<pre class="prettyprint lang-config">
-RewriteCond %{REQUEST_FILENAME}       !-f
+<pre class="prettyprint lang-config">RewriteCond %{REQUEST_FILENAME}       !-f
 RewriteCond %{REQUEST_FILENAME}       !-d
 RewriteRule ^/(.*) http://old.example.com/$1 [P]
-ProxyPassReverse / http://old.example.com/
-</pre>
+ProxyPassReverse / http://old.example.com/</pre>
 
     </dd>
 

Modified: httpd/httpd/trunk/docs/manual/rewrite/remapping.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/rewrite/remapping.html.en?rev=1564960&r1=1564959&r2=1564960&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/rewrite/remapping.html.en (original)
+++ httpd/httpd/trunk/docs/manual/rewrite/remapping.html.en Wed Feb  5 22:28:30 2014
@@ -74,10 +74,8 @@ configuration.</div>
       <p>We rewrite the old URL to the new one internally via the
       following rule:</p>
 
-<pre class="prettyprint lang-config">
-RewriteEngine  on
-RewriteRule    ^<strong>/foo</strong>\.html$  <strong>/bar</strong>.html [PT]
-</pre>
+<pre class="prettyprint lang-config">RewriteEngine  on
+RewriteRule    ^<strong>/foo</strong>\.html$  <strong>/bar</strong>.html [PT]</pre>
 
     </dd>
   </dl>
@@ -106,10 +104,8 @@ RewriteRule    ^<strong>/foo</strong>\.h
       <p>We force a HTTP redirect to the new URL which leads to a
       change of the browsers and thus the users view:</p>
 
-<pre class="prettyprint lang-config">
-RewriteEngine  on
-RewriteRule    ^<strong>/foo</strong>\.html$  <strong>bar</strong>.html  [<strong>R</strong>]
-</pre>
+<pre class="prettyprint lang-config">RewriteEngine  on
+RewriteRule    ^<strong>/foo</strong>\.html$  <strong>bar</strong>.html  [<strong>R</strong>]</pre>
 
 </dd>
 
@@ -150,18 +146,15 @@ RewriteRule    ^<strong>/foo</strong>\.h
 
 <pre class="prettyprint lang-config">#With mod_rewrite
 RewriteEngine on
-RewriteRule   ^/docs/(.+)  http://new.example.com/docs/$1  [R,L]
-</pre>
+RewriteRule   ^/docs/(.+)  http://new.example.com/docs/$1  [R,L]</pre>
 
 
 <pre class="prettyprint lang-config">#With RedirectMatch
-RedirectMatch ^/docs/(.*) http://new.example.com/docs/$1
-</pre>
+RedirectMatch ^/docs/(.*) http://new.example.com/docs/$1</pre>
 
 
 <pre class="prettyprint lang-config">#With Redirect
-Redirect /docs/ http://new.example.com/docs/
-</pre>
+Redirect /docs/ http://new.example.com/docs/</pre>
 
     </dd>
   </dl>
@@ -192,11 +185,9 @@ Redirect /docs/ http://new.example.com/d
       internally leads to the invocation of
       <code>/~quux/foo.cgi</code>.</p>
 
-<pre class="prettyprint lang-config">
-RewriteEngine  on
+<pre class="prettyprint lang-config">RewriteEngine  on
 RewriteBase    /~quux/
-RewriteRule    ^foo\.html$  foo.cgi &nbsp; [H=<strong>cgi-script</strong>]
-</pre>
+RewriteRule    ^foo\.html$  foo.cgi   [H=<strong>cgi-script</strong>]</pre>
 
     </dd>
   </dl>
@@ -224,8 +215,7 @@ RewriteRule    ^foo\.html$  foo.cgi &nbs
       existence of the new extension. If it exists, we take
       that name, else we rewrite the URL to its original state.</p>
 
-<pre class="prettyprint lang-config">
-#   backward compatibility ruleset for
+<pre class="prettyprint lang-config">#   backward compatibility ruleset for
 #   rewriting document.html to document.php
 #   when and only when document.php exists
 &lt;Directory /var/www/htdocs&gt;
@@ -235,8 +225,7 @@ RewriteRule    ^foo\.html$  foo.cgi &nbs
     RewriteCond $1.php -f
     RewriteCond $1.html !-f
     RewriteRule ^(.*).html$ $1.php
-&lt;/Directory&gt;
-</pre>
+&lt;/Directory&gt;</pre>
 
     </dd>
 
@@ -284,8 +273,7 @@ but rather uses the <code class="directi
 directive placed in a virtual host for the non-canonical
 hostname(s).</p>
 
-<pre class="prettyprint lang-config">
-&lt;VirtualHost *:80&gt;
+<pre class="prettyprint lang-config">&lt;VirtualHost *:80&gt;
   ServerName undesired.example.com
   ServerAlias example.com notthis.example.com
 
@@ -294,29 +282,24 @@ hostname(s).</p>
 
 &lt;VirtualHost *:80&gt;
   ServerName www.example.com
-&lt;/VirtualHost&gt;
-</pre>
+&lt;/VirtualHost&gt;</pre>
 
 
 <p>You can alternatively accomplish this using the
 <code class="directive"><a href="../mod/core.html#if">&lt;If&gt;</a></code>
 directive:</p>
 
-<pre class="prettyprint lang-config">
-&lt;If "%{HTTP_HOST} != 'www.example.com'"&gt;
+<pre class="prettyprint lang-config">&lt;If "%{HTTP_HOST} != 'www.example.com'"&gt;
 	Redirect / http://www.example.com/
-&lt;/If&gt;
-</pre>
+&lt;/If&gt;</pre>
 
 
 <p>Or, for example, to redirect a portion of your site to HTTPS, you
 might do the following:</p>
 
-<pre class="prettyprint lang-config">
-&lt;If "%{SERVER_PROTOCOL} != 'HTTPS'"&gt;
+<pre class="prettyprint lang-config">&lt;If "%{SERVER_PROTOCOL} != 'HTTPS'"&gt;
 	Redirect /admin/ https://www.example.com/admin/
-&lt;/If&gt;
-</pre>
+&lt;/If&gt;</pre>
 
 
 <p>If, for whatever reason, you still want to use <code>mod_rewrite</code>
@@ -324,20 +307,16 @@ might do the following:</p>
 you might use one of the recipes below.</p>
 
 <p>For sites running on a port other than 80:</p>
-<pre class="prettyprint lang-config">
-RewriteCond %{HTTP_HOST}   !^www\.example\.com [NC]
+<pre class="prettyprint lang-config">RewriteCond %{HTTP_HOST}   !^www\.example\.com [NC]
 RewriteCond %{HTTP_HOST}   !^$
 RewriteCond %{SERVER_PORT} !^80$
-RewriteRule ^/?(.*)         http://www.example.com:%{SERVER_PORT}/$1 [L,R,NE]
-</pre>
+RewriteRule ^/?(.*)         http://www.example.com:%{SERVER_PORT}/$1 [L,R,NE]</pre>
 
 
 <p>And for a site running on port 80</p>
-<pre class="prettyprint lang-config">
-RewriteCond %{HTTP_HOST}   !^www\.example\.com [NC]
+<pre class="prettyprint lang-config">RewriteCond %{HTTP_HOST}   !^www\.example\.com [NC]
 RewriteCond %{HTTP_HOST}   !^$
-RewriteRule ^/?(.*)         http://www.example.com/$1 [L,R,NE]
-</pre>
+RewriteRule ^/?(.*)         http://www.example.com/$1 [L,R,NE]</pre>
 
 
         <p>
@@ -347,11 +326,9 @@ RewriteRule ^/?(.*)         http://www.e
         <strong>example.com</strong>, you could use the following
         recipe:</p>
 
-<pre class="prettyprint lang-config">
-RewriteCond %{HTTP_HOST} !^www\. [NC]
+<pre class="prettyprint lang-config">RewriteCond %{HTTP_HOST} !^www\. [NC]
 RewriteCond %{HTTP_HOST} !^$
-RewriteRule ^/?(.*) http://www.%{HTTP_HOST}/$1 [L,R,NE]
-</pre>
+RewriteRule ^/?(.*) http://www.%{HTTP_HOST}/$1 [L,R,NE]</pre>
 
 
     <p>These rulesets will work either in your main server configuration
@@ -382,8 +359,7 @@ RewriteRule ^/?(.*) http://www.%{HTTP_HO
       resource, and, if not finding it in either place, will attempt to
       just serve it out of the location requested.</p>
 
-<pre class="prettyprint lang-config">
-RewriteEngine on
+<pre class="prettyprint lang-config">RewriteEngine on
 
 #   first try to find it in dir1/...
 #   ...and if found stop and be happy:
@@ -397,8 +373,7 @@ RewriteRule  ^(.+)  %{DOCUMENT_ROOT}/<st
 
 #   else go on for other Alias or ScriptAlias directives,
 #   etc.
-RewriteRule   ^  -  [PT]
-</pre>
+RewriteRule   ^  -  [PT]</pre>
 
     </dd>
   </dl>
@@ -427,13 +402,11 @@ RewriteRule   ^  -  [PT]
     <p>We'll use a <code class="directive"><a href="../mod/mod_rewrite.html#rewritemap">RewriteMap</a></code>
     directive to build a list of servers that we wish to use.</p>
 
-<pre class="prettyprint lang-config">
-HostnameLookups on
+<pre class="prettyprint lang-config">HostnameLookups on
 RewriteEngine on
 RewriteMap    multiplex         txt:/path/to/map.mirrors
 RewriteCond  %{REMOTE_HOST}     ([a-z]+)$ [NC]
-RewriteRule   ^/(.*)$  ${multiplex:<strong>%1</strong>|http://www.example.com/}$1  [R,L]
-</pre>
+RewriteRule   ^/(.*)$  ${multiplex:<strong>%1</strong>|http://www.example.com/}$1  [R,L]</pre>
 
 
 <div class="example"><p><code>
@@ -488,16 +461,14 @@ com       http://www.example.com/<br />
       All other browsers receive page <code>foo.32.html</code>.
       This is done with the following ruleset:</p>
 
-<pre class="prettyprint lang-config">
-RewriteCond %{HTTP_USER_AGENT}  ^<strong>Mozilla/3</strong>.*
+<pre class="prettyprint lang-config">RewriteCond %{HTTP_USER_AGENT}  ^<strong>Mozilla/3</strong>.*
 RewriteRule ^foo\.html$         foo.<strong>NS</strong>.html          [<strong>L</strong>]
 
 RewriteCond %{HTTP_USER_AGENT}  ^Lynx/ [OR]
 RewriteCond %{HTTP_USER_AGENT}  ^Mozilla/[12]
 RewriteRule ^foo\.html$         foo.<strong>20</strong>.html          [<strong>L</strong>]
 
-RewriteRule ^foo\.html$         foo.<strong>32</strong>.html          [<strong>L</strong>]
-</pre>
+RewriteRule ^foo\.html$         foo.<strong>32</strong>.html          [<strong>L</strong>]</pre>
 
     </dd>
   </dl>
@@ -538,7 +509,7 @@ RewriteRule ^foo\.html$         foo.<str
      This should really be accomplished with Redirect or RedirectMatch
      directives:
 
-     <pre class="prettyprint lang-config"> RedirectMatch ^/(puppies|canines)/(.*) /dogs/$2 </pre>
+     <pre class="prettyprint lang-config"> RedirectMatch ^/(puppies|canines)/(.*) /dogs/$2</pre>
 
      </dd>
       </dl>
@@ -568,10 +539,8 @@ using the following ruleset:</p>
       <code>/about/</code>:
       </p>
 
-<pre class="prettyprint lang-config">
-RewriteEngine on
-RewriteRule   ^/$  /about/  [<strong>R</strong>]
-</pre>
+<pre class="prettyprint lang-config">RewriteEngine on
+RewriteRule   ^/$  /about/  [<strong>R</strong>]</pre>
 
 
 <p>Note that this can also be handled using the <code class="directive"><a href="../mod/mod_alias.html#redirectmatch">RedirectMatch</a></code> directive:</p>
@@ -605,26 +574,22 @@ that should go to an existing resource s
 <dd>
 <p>As of version 2.2.16, you should use the <code class="directive"><a href="../mod/mod_dir.html#fallbackresource">FallbackResource</a></code> directive for this:</p>
 
-<pre class="prettyprint lang-config">
-&lt;Directory /var/www/my_blog&gt;
+<pre class="prettyprint lang-config">&lt;Directory /var/www/my_blog&gt;
   FallbackResource index.php
-&lt;/Directory&gt;
-</pre>
+&lt;/Directory&gt;</pre>
 
 
 <p>However, in earlier versions of Apache, or if your needs are more
 complicated than this, you can use a variation of the following rewrite
 set to accomplish the same thing:</p>
 
-<pre class="prettyprint lang-config">
-&lt;Directory /var/www/my_blog&gt;
+<pre class="prettyprint lang-config">&lt;Directory /var/www/my_blog&gt;
   RewriteBase /my_blog
 
   RewriteCond /var/www/my_blog/%{REQUEST_FILENAME} !-f
   RewriteCond /var/www/my_blog/%{REQUEST_FILENAME} !-d
   RewriteRule ^ index.php [PT]
-&lt;/Directory&gt;
-</pre>
+&lt;/Directory&gt;</pre>
 
 
 <p>If, on the other hand, you wish to pass the requested URI as a query

Modified: httpd/httpd/trunk/docs/manual/rewrite/rewritemap.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/rewrite/rewritemap.html.en?rev=1564960&r1=1564959&r2=1564960&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/rewrite/rewritemap.html.en (original)
+++ httpd/httpd/trunk/docs/manual/rewrite/rewritemap.html.en Wed Feb  5 22:28:30 2014
@@ -146,11 +146,8 @@ may be used, and give examples of each.<
     </p>
 
    <p> <strong>Redirect a URI to an all-lowercase version of itself</strong></p>
-    <pre class="prettyprint lang-config">
-
-RewriteMap lc int:tolower
-RewriteRule (.*?[A-Z]+.*) ${lc:$1} [R]
-    </pre>
+    <pre class="prettyprint lang-config">RewriteMap lc int:tolower
+RewriteRule (.*?[A-Z]+.*) ${lc:$1} [R]</pre>
 
 
     <div class="note">
@@ -187,10 +184,8 @@ RewriteRule (.*?[A-Z]+.*) ${lc:$1} [R]
     product IDs for easier-to-remember URLs, using the following
     recipe:</p>
 <p><strong>Product to ID configuration</strong></p>
-    <pre class="prettyprint lang-config">
-RewriteMap product2id txt:/etc/apache2/productmap.txt
-RewriteRule ^/product/(.*) /prods.php?id=${product2id:$1|NOTFOUND} [PT]
-    </pre>
+    <pre class="prettyprint lang-config">RewriteMap product2id txt:/etc/apache2/productmap.txt
+RewriteRule ^/product/(.*) /prods.php?id=${product2id:$1|NOTFOUND} [PT]</pre>
 
 
     <p>We assume here that the <code>prods.php</code> script knows what
@@ -260,12 +255,10 @@ static   www1|www2|www3|www4<br />
 dynamic  www5|www6
     </code></p></div>
 <p><strong>Configuration directives</strong></p>
-    <pre class="prettyprint lang-config">
-RewriteMap servers rnd:/path/to/file/map.txt
+    <pre class="prettyprint lang-config">RewriteMap servers rnd:/path/to/file/map.txt
 
 RewriteRule ^/(.*\.(png|gif|jpg)) http://${servers:static}/$1 [NC,P,L]
-RewriteRule ^/(.*) http://${servers:dynamic}/$1 [P,L]
-    </pre>
+RewriteRule ^/(.*) http://${servers:dynamic}/$1 [P,L]</pre>
 
 
     <p>So, when an image is requested and the first of these rules is
@@ -297,9 +290,7 @@ static   www1|www1|www2|www3|www4
 
     <p>You may optionally specify a particular dbm type:</p>
 
- <pre class="prettyprint lang-config">
-RewriteMap examplemap dbm=sdbm:/etc/apache/mapfile.dbm
- </pre>
+ <pre class="prettyprint lang-config">RewriteMap examplemap dbm=sdbm:/etc/apache/mapfile.dbm</pre>
 
 
     <p>The type can be sdbm, gdbm, ndbm or db.
@@ -318,9 +309,7 @@ $ httxt2dbm -i mapfile.txt -o mapfile.ma
 <p>You can then reference the resulting file in your
 <code>RewriteMap</code> directive:</p>
 
-<pre class="prettyprint lang-config">
-RewriteMap mapname dbm:/etc/apache/mapfile.map
-</pre>
+<pre class="prettyprint lang-config">RewriteMap mapname dbm:/etc/apache/mapfile.map</pre>
 
 
 <div class="note">
@@ -371,22 +360,17 @@ by many requests.
     underscores in a request URI.</p>
     
 <p><strong>Rewrite configuration</strong></p>
-    <pre class="prettyprint lang-config">
-
-RewriteMap d2u prg:/www/bin/dash2under.pl<br />
-RewriteRule - ${d2u:%{REQUEST_URI}}
-    </pre>
+    <pre class="prettyprint lang-config">RewriteMap d2u prg:/www/bin/dash2under.pl<br />
+RewriteRule - ${d2u:%{REQUEST_URI}}</pre>
 
 
     <p><strong>dash2under.pl</strong></p>
-    <pre class="prettyprint lang-perl">
-    #!/usr/bin/perl
+    <pre class="prettyprint lang-perl">    #!/usr/bin/perl
     $| = 1; # Turn off I/O buffering
     while (&lt;STDIN&gt;) {
         s/-/_/g; # Replace dashes with underscores
         print $_;
-    }
-    </pre>
+    }</pre>
 
 
 <div class="note"><h3>Caution!</h3>
@@ -429,9 +413,7 @@ this process, or if the script itself is
     <p>If a query returns more than one row, a random row from
 the result set is used.</p>
 
-	<div class="example"><h3>Example</h3><pre class="prettyprint lang-config">
-RewriteMap myquery "fastdbd:SELECT destination FROM rewrite WHERE source = %s"
-    </pre>
+	<div class="example"><h3>Example</h3><pre class="prettyprint lang-config">RewriteMap myquery "fastdbd:SELECT destination FROM rewrite WHERE source = %s"</pre>
 </div>
 
   </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>

Modified: httpd/httpd/trunk/docs/manual/rewrite/vhosts.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/rewrite/vhosts.html.en?rev=1564960&r1=1564959&r2=1564960&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/rewrite/vhosts.html.en (original)
+++ httpd/httpd/trunk/docs/manual/rewrite/vhosts.html.en Wed Feb  5 22:28:30 2014
@@ -65,14 +65,12 @@ mod_rewrite</a> document.</div>
 
     <dd>
 
-<pre class="prettyprint lang-config">
-RewriteEngine on
+<pre class="prettyprint lang-config">RewriteEngine on
 
 RewriteMap    lowercase int:tolower
 
 RewriteCond   ${lowercase:%{<strong>HTTP_HOST</strong>}}   ^www\.<strong>([^.]+)</strong>\.example\.com$
-RewriteRule   ^(.*) /home/<strong>%1</strong>/www$1
-</pre>
+RewriteRule   ^(.*) /home/<strong>%1</strong>/www$1</pre>
 </dd>
 
 <dt>Discussion</dt>
@@ -123,8 +121,7 @@ dynamic content, and Alias resolution.
     any <code>ScriptAlias</code> directives, we must have
     <code>mod_rewrite</code> explicitly enact those mappings.</p>
 
-<pre class="prettyprint lang-config">
-# get the server name from the Host: header
+<pre class="prettyprint lang-config"># get the server name from the Host: header
 UseCanonicalName Off
 
 # splittable logs
@@ -152,8 +149,7 @@ RewriteRule  ^/(.*)$  /www/hosts/${lower
 
 ## and now deal with CGIs - we have to force a handler
 RewriteCond  %{REQUEST_URI}  ^/cgi-bin/
-RewriteRule  ^/(.*)$  /www/hosts/${lowercase:%{SERVER_NAME}}/cgi-bin/$1  [H=cgi-script]
-</pre>
+RewriteRule  ^/(.*)$  /www/hosts/${lowercase:%{SERVER_NAME}}/cgi-bin/$1  [H=cgi-script]</pre>
 
 
 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
@@ -177,8 +173,7 @@ customer-N.example.com  /www/customers/N
 
     <p>The <code>httpd.conf</code> should contain the following:</p>
 
-<pre class="prettyprint lang-config">
-RewriteEngine on
+<pre class="prettyprint lang-config">RewriteEngine on
 
 RewriteMap   lowercase  int:tolower
 
@@ -196,8 +191,7 @@ RewriteRule  ^/(.*)$                    
 RewriteCond  %{REQUEST_URI}               ^/cgi-bin/
 RewriteCond  ${lowercase:%{SERVER_NAME}}  ^(.+)$
 RewriteCond  ${vhost:%1}                  ^(/.*)$
-RewriteRule  ^/(.*)$                      %1/cgi-bin/$1 [H=cgi-script]
-</pre>
+RewriteRule  ^/(.*)$                      %1/cgi-bin/$1 [H=cgi-script]</pre>
 
 
 </div></div>

Modified: httpd/httpd/trunk/docs/manual/sections.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/sections.html.en?rev=1564960&r1=1564959&r2=1564960&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/sections.html.en (original)
+++ httpd/httpd/trunk/docs/manual/sections.html.en Wed Feb  5 22:28:30 2014
@@ -62,11 +62,9 @@ with the following configuration, all re
 to another site only if the server is started using
 <code>httpd -DClosedForNow</code>:</p>
 
-<pre class="prettyprint lang-config">
-&lt;IfDefine ClosedForNow&gt;
+<pre class="prettyprint lang-config">&lt;IfDefine ClosedForNow&gt;
     Redirect / http://otherserver.example.com/
-&lt;/IfDefine&gt;
-</pre>
+&lt;/IfDefine&gt;</pre>
 
 
 <p>The <code class="directive"><a href="./mod/core.html#ifmodule">&lt;IfModule&gt;</a></code>
@@ -83,11 +81,9 @@ about missing modules.</p>
 <p>In the following example, the <code class="directive"><a href="./mod/mod_mime_magic.html#mimemagicfile">MimeMagicFile</a></code> directive will be
 applied only if <code class="module"><a href="./mod/mod_mime_magic.html">mod_mime_magic</a></code> is available.</p>
 
-<pre class="prettyprint lang-config">
-&lt;IfModule mod_mime_magic.c&gt;
+<pre class="prettyprint lang-config">&lt;IfModule mod_mime_magic.c&gt;
     MimeMagicFile conf/magic
-&lt;/IfModule&gt;
-</pre>
+&lt;/IfModule&gt;</pre>
 
 
 <p>The <code class="directive"><a href="./mod/mod_version.html#ifversion">&lt;IfVersion&gt;</a></code>
@@ -96,12 +92,10 @@ only be applied if a particular version 
 module is designed for the use in test suites and large networks which have to
 deal with different httpd versions and different configurations.</p>
 
-<pre class="prettyprint lang-config">
-&lt;IfVersion &gt;= 2.4&gt;
+<pre class="prettyprint lang-config">&lt;IfVersion &gt;= 2.4&gt;
     # this happens only in versions greater or
     # equal 2.4.0.
-&lt;/IfVersion&gt;
-</pre>
+&lt;/IfVersion&gt;</pre>
 
 
 <p><code class="directive"><a href="./mod/core.html#ifdefine">&lt;IfDefine&gt;</a></code>,
@@ -144,11 +138,9 @@ The same effect can be obtained using <a
 following configuration, directory indexes will be enabled for the
 <code>/var/web/dir1</code> directory and all subdirectories.</p>
 
-<pre class="prettyprint lang-config">
-&lt;Directory /var/web/dir1&gt;
+<pre class="prettyprint lang-config">&lt;Directory /var/web/dir1&gt;
     Options +Indexes
-&lt;/Directory&gt;
-</pre>
+&lt;/Directory&gt;</pre>
 
 
 <p>Directives enclosed in a <code class="directive"><a href="./mod/core.html#files">&lt;Files&gt;</a></code> section apply to any file with
@@ -158,11 +150,9 @@ when placed in the main section of the c
 deny access to any file named <code>private.html</code> regardless
 of where it is found.</p>
 
-<pre class="prettyprint lang-config">
-&lt;Files private.html&gt;
+<pre class="prettyprint lang-config">&lt;Files private.html&gt;
     Require all denied
-&lt;/Files&gt;
-</pre>
+&lt;/Files&gt;</pre>
 
 
 <p>To address files found in a particular part of the filesystem, the
@@ -175,13 +165,11 @@ access to <code>/var/web/dir1/private.ht
 of <code>private.html</code> found under the <code>/var/web/dir1/</code>
 directory.</p>
 
-<pre class="prettyprint lang-config">
-&lt;Directory /var/web/dir1&gt;
+<pre class="prettyprint lang-config">&lt;Directory /var/web/dir1&gt;
     &lt;Files private.html&gt;
         Require all denied
     &lt;/Files&gt;
-&lt;/Directory&gt;
-</pre>
+&lt;/Directory&gt;</pre>
 
 
 
@@ -198,11 +186,9 @@ In particular, it will apply to requests
 <code>http://yoursite.example.com/private/dir/file.html</code> as well
 as any other requests starting with the <code>/private</code> string.</p>
 
-<pre class="prettyprint lang-config">
-&lt;LocationMatch ^/private&gt;
+<pre class="prettyprint lang-config">&lt;LocationMatch ^/private&gt;
     Require all denied
-&lt;/LocationMatch&gt;
-</pre>
+&lt;/LocationMatch&gt;</pre>
 
 
 <p>The <code class="directive"><a href="./mod/core.html#location">&lt;Location&gt;</a></code>
@@ -212,11 +198,9 @@ URL to an internal Apache HTTP Server ha
 No file called <code>server-status</code> needs to exist in the
 filesystem.</p>
 
-<pre class="prettyprint lang-config">
-&lt;Location /server-status&gt;
+<pre class="prettyprint lang-config">&lt;Location /server-status&gt;
     SetHandler server-status
-&lt;/Location&gt;
-</pre>
+&lt;/Location&gt;</pre>
 
 
 
@@ -224,26 +208,20 @@ filesystem.</p>
 <p>In order to have two overlapping URLs one has to consider the order in which
 certain sections or directives are evaluated. For
 <code class="directive"><a href="./mod/core.html#location">&lt;Location&gt;</a></code> this would be:</p>
-<pre class="prettyprint lang-config">
-&lt;Location /foo&gt;
+<pre class="prettyprint lang-config">&lt;Location /foo&gt;
 &lt;/Location&gt;
 &lt;Location /foo/bar&gt;
-&lt;/Location&gt;
-</pre>
+&lt;/Location&gt;</pre>
 
 <p><code class="directive"><a href="./mod/mod_alias.html#alias">&lt;Alias&gt;</a></code>es on the other hand,
 are mapped vice-versa:</p>
-<pre class="prettyprint lang-config">
-Alias /foo/bar /srv/www/uncommon/bar
-Alias /foo /srv/www/common/foo
-</pre>
+<pre class="prettyprint lang-config">Alias /foo/bar /srv/www/uncommon/bar
+Alias /foo /srv/www/common/foo</pre>
 
 <p>The same is true for the <code class="directive"><a href="./mod/mod_proxy.html#proxypass">ProxyPass</a></code>
 directives:</p>
-<pre class="prettyprint lang-config">
-ProxyPass /special-area http://special.example.com smax=5 max=10
-ProxyPass / balancer://mycluster/ stickysession=JSESSIONID|jsessionid nofailover=On
-</pre>
+<pre class="prettyprint lang-config">ProxyPass /special-area http://special.example.com smax=5 max=10
+ProxyPass / balancer://mycluster/ stickysession=JSESSIONID|jsessionid nofailover=On</pre>
 
 
 
@@ -270,20 +248,16 @@ how directives are applied.</p>
 <p>A non-regex wildcard section that changes the configuration of
 all user directories could look as follows:</p>
 
-<pre class="prettyprint lang-config">
-&lt;Directory /home/*/public_html&gt;
+<pre class="prettyprint lang-config">&lt;Directory /home/*/public_html&gt;
     Options Indexes
-&lt;/Directory&gt;
-</pre>
+&lt;/Directory&gt;</pre>
 
 
 <p>Using regex sections, we can deny access to many types of image files
 at once:</p>
-<pre class="prettyprint lang-config">
-&lt;FilesMatch \.(?i:gif|jpe?g|png)$&gt;
+<pre class="prettyprint lang-config">&lt;FilesMatch \.(?i:gif|jpe?g|png)$&gt;
     Require all denied
-&lt;/FilesMatch&gt;
-</pre>
+&lt;/FilesMatch&gt;</pre>
 
 
 <p>Regular expressions containing <strong>named groups and
@@ -292,11 +266,9 @@ corresponding name in uppercase. This al
 and URLs to be referenced from within <a href="expr.html">expressions</a>
 and modules like <code class="module"><a href="./mod/mod_rewrite.html">mod_rewrite</a></code>.</p>
 
-<pre class="prettyprint lang-config">
-&lt;DirectoryMatch ^/var/www/combined/(?&lt;SITENAME&gt;[^/]+)&gt;
+<pre class="prettyprint lang-config">&lt;DirectoryMatch ^/var/www/combined/(?&lt;SITENAME&gt;[^/]+)&gt;
     require ldap-group cn=%{env:SITENAME},ou=combined,o=Example
-&lt;/DirectoryMatch&gt;
-</pre>
+&lt;/DirectoryMatch&gt;</pre>
 
 
 
@@ -307,11 +279,9 @@ directive change the configuration depen
 expressed by a boolean expression. For example, the following configuration
 denies access if the HTTP Referer header does not start with
 "http://www.example.com/".</p>
-<pre class="prettyprint lang-config">
-&lt;If "!(%{HTTP_REFERER} -strmatch 'http://www.example.com/*')"&gt;
+<pre class="prettyprint lang-config">&lt;If "!(%{HTTP_REFERER} -strmatch 'http://www.example.com/*')"&gt;
     Require all denied
-&lt;/If&gt;
-</pre>
+&lt;/If&gt;</pre>
 
 
 
@@ -330,11 +300,9 @@ different webspace locations (URLs) coul
 location, allowing your restrictions to be circumvented.
 For example, consider the following configuration:</p>
 
-<pre class="prettyprint lang-config">
-&lt;Location /dir/&gt;
+<pre class="prettyprint lang-config">&lt;Location /dir/&gt;
     Require all denied
-&lt;/Location&gt;
-</pre>
+&lt;/Location&gt;</pre>
 
 
 <p>This works fine if the request is for
@@ -395,11 +363,9 @@ that match the specified URL.  For examp
 will prevent the proxy server from being used to access the
 <code>www.example.com</code> website.</p>
 
-<pre class="prettyprint lang-config">
-&lt;Proxy http://www.example.com/*&gt;
+<pre class="prettyprint lang-config">&lt;Proxy http://www.example.com/*&gt;
     Require all granted
-&lt;/Proxy&gt;
-</pre>
+&lt;/Proxy&gt;</pre>
 
 </div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
 <div class="section">
@@ -508,8 +474,7 @@ merging. Assuming they all apply to the 
 this example will be applied in the order A &gt; B &gt; C &gt; D &gt;
 E.</p>
 
-<pre class="prettyprint lang-config">
-&lt;Location /&gt;
+<pre class="prettyprint lang-config">&lt;Location /&gt;
     E
 &lt;/Location&gt;
 
@@ -529,9 +494,7 @@ E.</p>
 
 &lt;Directory /a/b&gt;
     A
-&lt;/Directory&gt;
-
-</pre>
+&lt;/Directory&gt;</pre>
 
 
 <p>For a more concrete example, consider the following.  Regardless of
@@ -539,8 +502,7 @@ any access restrictions placed in <code 
 evaluated last and will allow unrestricted access to the server.  In
 other words, order of merging is important, so be careful!</p>
 
-<pre class="prettyprint lang-config">
-&lt;Location /&gt;
+<pre class="prettyprint lang-config">&lt;Location /&gt;
     Require all granted
 &lt;/Location&gt;
 
@@ -550,8 +512,7 @@ other words, order of merging is importa
         Require all granted
         Require not host badguy.example.com
     &lt;/RequireAll&gt;
-&lt;/Directory&gt;
-</pre>
+&lt;/Directory&gt;</pre>
 
 
 

Modified: httpd/httpd/trunk/docs/manual/sections.html.fr
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/sections.html.fr?rev=1564960&r1=1564959&r2=1564960&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/sections.html.fr (original)
+++ httpd/httpd/trunk/docs/manual/sections.html.fr Wed Feb  5 22:28:30 2014
@@ -68,11 +68,9 @@ avec la configuration suivante, toutes l
 un autre site si le serveur est démarré en utilisant la ligne de commande :
 <code>httpd -DClosedForNow</code>:</p>
 
-<pre class="prettyprint lang-config">
-&lt;IfDefine ClosedForNow&gt;
+<pre class="prettyprint lang-config">&lt;IfDefine ClosedForNow&gt;
     Redirect / http://otherserver.example.com/
-&lt;/IfDefine&gt;
-</pre>
+&lt;/IfDefine&gt;</pre>
 
 
 <p>Le conteneur <code class="directive"><a href="./mod/core.html#ifmodule">&lt;IfModule&gt;</a></code>
@@ -90,11 +88,9 @@ systématiquement, car vous pouvez perdr
 <p>Dans l'exemple suivant, la directive <code class="directive"><a href="./mod/mod_mime_magic.html#mimemagicfile">MimeMagicFile</a></code> ne s'appliquera que si le
 module <code class="module"><a href="./mod/mod_mime_magic.html">mod_mime_magic</a></code> est disponible.</p>
 
-<pre class="prettyprint lang-config">
-&lt;IfModule mod_mime_magic.c&gt;
+<pre class="prettyprint lang-config">&lt;IfModule mod_mime_magic.c&gt;
     MimeMagicFile conf/magic
-&lt;/IfModule&gt;
-</pre>
+&lt;/IfModule&gt;</pre>
 
 
 <p>Le conteneur
@@ -105,12 +101,10 @@ conteneur a été conçu pour une utilis
 et les grands réseaux qui doivent prendre en compte différentes versions
 et configurations de httpd.</p>
 
-<pre class="prettyprint lang-config">
-&lt;IfVersion &gt;= 2.4&gt;
+<pre class="prettyprint lang-config">&lt;IfVersion &gt;= 2.4&gt;
     # les directives situées ici ne s'appliquent que si la version <br />
     # est supérieure ou égale à 2.4.0.
-&lt;/IfVersion&gt;
-</pre>
+&lt;/IfVersion&gt;</pre>
 
 
 <p><code class="directive"><a href="./mod/core.html#ifdefine">&lt;IfDefine&gt;</a></code>,
@@ -160,11 +154,9 @@ Le même effet peut être obtenu en util
 configuration suivante, l'indexation sera activée pour le répertoire
 <code>/var/web/dir1</code> et tous ses sous-répertoires.</p>
 
-<pre class="prettyprint lang-config">
-&lt;Directory /var/web/dir1&gt;
+<pre class="prettyprint lang-config">&lt;Directory /var/web/dir1&gt;
     Options +Indexes
-&lt;/Directory&gt;
-</pre>
+&lt;/Directory&gt;</pre>
 
 
 <p>Les directives contenues dans une section <code class="directive"><a href="./mod/core.html#files">&lt;Files&gt;</a></code> s'appliquent à tout fichier
@@ -174,11 +166,9 @@ placées dans la section principale du f
 l'accès à tout fichier nommé <code>private.html</code> quel que soit
 l'endroit où il se trouve.</p>
 
-<pre class="prettyprint lang-config">
-&lt;Files private.html&gt;
+<pre class="prettyprint lang-config">&lt;Files private.html&gt;
     Require all denied
-&lt;/Files&gt;
-</pre>
+&lt;/Files&gt;</pre>
 
 
 <p>Pour faire référence à des fichiers qui se trouvent en des points
@@ -192,13 +182,11 @@ l'accès à <code>/var/web/dir1/private.
 <code>private.html</code> qui se trouve dans l'arborescence
 <code>/var/web/dir1/</code>.</p>
 
-<pre class="prettyprint lang-config">
-&lt;Directory /var/web/dir1&gt;
+<pre class="prettyprint lang-config">&lt;Directory /var/web/dir1&gt;
     &lt;Files private.html&gt;
         Require all denied
     &lt;/Files&gt;
-&lt;/Directory&gt;
-</pre>
+&lt;/Directory&gt;</pre>
 
 
 
@@ -216,11 +204,9 @@ En particulier, l'interdiction s'appliqu
 <code>http://yoursite.example.com/private/dir/file.html</code> ainsi qu'à
 toute requête commençant par la chaîne de caractères <code>/private</code>.</p>
 
-<pre class="prettyprint lang-config">
-&lt;LocationMatch ^/private&gt;
+<pre class="prettyprint lang-config">&lt;LocationMatch ^/private&gt;
     Require all denied
-&lt;/LocationMatch&gt;
-</pre>
+&lt;/LocationMatch&gt;</pre>
 
 
 <p>Le conteneur <code class="directive"><a href="./mod/core.html#location">&lt;Location&gt;</a></code>
@@ -231,11 +217,9 @@ particulière vers un gestionnaire inter
 Il n'est pas nécessaire de trouver un fichier nommé <code>server-status</code>
 dans le système de fichiers.</p>
 
-<pre class="prettyprint lang-config">
-&lt;Location /server-status&gt;
+<pre class="prettyprint lang-config">&lt;Location /server-status&gt;
     SetHandler server-status
-&lt;/Location&gt;
-</pre>
+&lt;/Location&gt;</pre>
 
 
 
@@ -244,24 +228,18 @@ dans le système de fichiers.</p>
 dans lequel certaines sections ou directives sont évaluées. Pour
 <code class="directive"><a href="./mod/core.html#location">&lt;Location&gt;</a></code>, on doit
 avoir :</p>
-<pre class="prettyprint lang-config">
-&lt;Location /foo&gt;
+<pre class="prettyprint lang-config">&lt;Location /foo&gt;
 &lt;/Location&gt;
 &lt;Location /foo/bar&gt;
-&lt;/Location&gt;
-</pre>
+&lt;/Location&gt;</pre>
 
 <p>Les directives <code class="directive"><a href="./mod/mod_alias.html#alias">&lt;Alias&gt;</a></code>, quant à elles, sont évaluées vice-versa :</p>
-<pre class="prettyprint lang-config">
-Alias /foo/bar /srv/www/uncommon/bar
-Alias /foo /srv/www/common/foo
-</pre>
+<pre class="prettyprint lang-config">Alias /foo/bar /srv/www/uncommon/bar
+Alias /foo /srv/www/common/foo</pre>
 
 <p>Ceci est aussi vrai pour les directives <code class="directive"><a href="./mod/mod_proxy.html#proxypass">ProxyPass</a></code> :</p>
-<pre class="prettyprint lang-config">
-ProxyPass /special-area http://special.example.com smax=5 max=10
-ProxyPass / balancer://mycluster/ stickysession=JSESSIONID|jsessionid nofailover=On
-</pre>
+<pre class="prettyprint lang-config">ProxyPass /special-area http://special.example.com smax=5 max=10
+ProxyPass / balancer://mycluster/ stickysession=JSESSIONID|jsessionid nofailover=On</pre>
 
 
 
@@ -297,21 +275,17 @@ répertoires utilisateurs à l'aide de c
 mais sans utiliser
 les expressions rationnelles pourrait ressembler à ceci :</p>
 
-<pre class="prettyprint lang-config">
-&lt;Directory /home/*/public_html&gt;
+<pre class="prettyprint lang-config">&lt;Directory /home/*/public_html&gt;
     Options Indexes
-&lt;/Directory&gt;
-</pre>
+&lt;/Directory&gt;</pre>
 
 
 <p>Avec les conteneurs utilisant les expressions rationnelles,
 on peut interdire l'accès à de nombreux types de fichiers d'images
 simultanément :</p>
-<pre class="prettyprint lang-config">
-+&lt;FilesMatch \.(?i:gif|jpe?g|png)$&gt;
+<pre class="prettyprint lang-config">+&lt;FilesMatch \.(?i:gif|jpe?g|png)$&gt;
     Require all denied
-&lt;/FilesMatch&gt;
-</pre>
+&lt;/FilesMatch&gt;</pre>
 
 
 <p>Les expressions rationnelles contenant des <strong>groupes nommés et
@@ -320,11 +294,9 @@ leur nom en majuscules. Ceci permet de r
 chemins de fichiers et d'URLs depuis une <a href="expr.html">expression</a> et au sein de modules comme
 <code class="module"><a href="./mod/mod_rewrite.html">mod_rewrite</a></code>.</p>
 
-<pre class="prettyprint lang-config">
-&lt;DirectoryMatch ^/var/www/combined/(?&lt;SITENAME&gt;[^/]+)&gt;
+<pre class="prettyprint lang-config">&lt;DirectoryMatch ^/var/www/combined/(?&lt;SITENAME&gt;[^/]+)&gt;
     require ldap-group cn=%{env:SITENAME},ou=combined,o=Example
-&lt;/DirectoryMatch&gt;
-</pre>
+&lt;/DirectoryMatch&gt;</pre>
 
 
 
@@ -335,11 +307,9 @@ permet de modifier la configuration en f
 être définie sous la forme d'une expression booléenne. Dans l'exemple
 suivant, l'accès est interdit si l'en-tête HTTP Referer ne commence pas
 par "http://www.example.com/".</p>
-<pre class="prettyprint lang-config">
-&lt;If "!(%{HTTP_REFERER} -strmatch 'http://www.example.com/*')"&gt;
+<pre class="prettyprint lang-config">&lt;If "!(%{HTTP_REFERER} -strmatch 'http://www.example.com/*')"&gt;
     Require all denied
-&lt;/If&gt;
-</pre>
+&lt;/If&gt;</pre>
 
 
 
@@ -359,11 +329,9 @@ l'arborescence du site web (URLs) peuven
 du système de fichier, ce qui peut permettre de contourner vos restrictions.
 Par exemple, imaginez la configuration suivante :</p>
 
-<pre class="prettyprint lang-config">
-&lt;Location /dir/&gt;
+<pre class="prettyprint lang-config">&lt;Location /dir/&gt;
     Require all denied
-&lt;/Location&gt;
-</pre>
+&lt;/Location&gt;</pre>
 
 
 <p>Elle fonctionne correctement si la requête appelle
@@ -434,11 +402,9 @@ Par exemple, la configuration suivante
 va interdire l'utilisation du serveur proxy pour accéder au site
 <code>www.example.com</code>.</p>
 
-<pre class="prettyprint lang-config">
-&lt;Proxy http://www.example.com/*&gt;
+<pre class="prettyprint lang-config">&lt;Proxy http://www.example.com/*&gt;
     Require all granted
-&lt;/Proxy&gt;
-</pre>
+&lt;/Proxy&gt;</pre>
 
 </div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
 <div class="section">
@@ -558,8 +524,7 @@ En supposant qu'elles s'appliquent toute
 cet exemple seront appliquées dans l'ordre suivant : A &gt; B &gt; C &gt; D &gt;
 E.</p>
 
-<pre class="prettyprint lang-config">
-&lt;Location /&gt;
+<pre class="prettyprint lang-config">&lt;Location /&gt;
     E
 &lt;/Location&gt;
 
@@ -579,9 +544,7 @@ E.</p>
 
 &lt;Directory /a/b&gt;
     A
-&lt;/Directory&gt;
-
-</pre>
+&lt;/Directory&gt;</pre>
 
 
 <p>Pour un exemple plus concret, considérez ce qui suit.  Sans tenir compte
@@ -590,8 +553,7 @@ de toute restriction d'accès placée da
 En d'autres termes, l'ordre de la combinaison des sections est important,
 soyez donc prudent !</p>
 
-<pre class="prettyprint lang-config">
-&lt;Location /&gt;
+<pre class="prettyprint lang-config">&lt;Location /&gt;
     Require all granted
 &lt;/Location&gt;
 
@@ -601,8 +563,7 @@ soyez donc prudent !</p>
         Require all granted
         Require not host badguy.example.com
     &lt;/RequireAll&gt;
-&lt;/Directory&gt;
-</pre>
+&lt;/Directory&gt;</pre>
 
 
 



Mime
View raw message