httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rbo...@apache.org
Subject svn commit: r1059175 - in /httpd/httpd/trunk/docs/manual/rewrite: advanced.html.en proxy.html.en remapping.html.en rewritemap.html.en
Date Fri, 14 Jan 2011 21:18:27 GMT
Author: rbowen
Date: Fri Jan 14 21:18:27 2011
New Revision: 1059175

URL: http://svn.apache.org/viewvc?rev=1059175&view=rev
Log:
Rebuild HTML.

Modified:
    httpd/httpd/trunk/docs/manual/rewrite/advanced.html.en
    httpd/httpd/trunk/docs/manual/rewrite/proxy.html.en
    httpd/httpd/trunk/docs/manual/rewrite/remapping.html.en
    httpd/httpd/trunk/docs/manual/rewrite/rewritemap.html.en

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=1059175&r1=1059174&r2=1059175&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/rewrite/advanced.html.en (original)
+++ httpd/httpd/trunk/docs/manual/rewrite/advanced.html.en Fri Jan 14 21:18:27 2011
@@ -64,37 +64,37 @@ configuration.</div>
       <p>A mapping is maintained, from users to target servers, in
       external map files. They look like:</p>
 
-<div class="example"><pre>
-user1  physical_host_of_user1
-user2  physical_host_of_user2
+<div class="example"><p><code>
+user1  physical_host_of_user1<br />
+user2  physical_host_of_user2<br />
 :      :
-</pre></div>
+</code></p></div>
 
   <p>We put this into a <code>map.users-to-hosts</code> file. The
     aim is to map;</p>
 
-<div class="example"><pre>
+<div class="example"><p><code>
 /u/user1/anypath
-</pre></div>
+</code></p></div>
 
   <p>to</p>
 
-<div class="example"><pre>
+<div class="example"><p><code>
 http://physical_host_of_user1/u/user/anypath
-</pre></div>
+</code></p></div>
 
       <p>thus every URL path need not be valid on every backend physical
       host. The following ruleset does this for us with the help of the map
       files assuming that server0 is a default server which will be used if
       a user has no entry in the map:</p>
 
-<div class="example"><pre>
-RewriteEngine on
-
-RewriteMap      users-to-hosts   txt:/path/to/map.users-to-hosts
-
+<div class="example"><p><code>
+RewriteEngine on<br />
+<br />
+RewriteMap      users-to-hosts   txt:/path/to/map.users-to-hosts<br />
+<br />
 RewriteRule   ^/u/<strong>([^/]+)</strong>/?(.*)   http://<strong>${users-to-hosts:$1|server0}</strong>/u/$1/$2
-</pre></div>
+</code></p></div>
     </dd>
   </dl>
 
@@ -120,11 +120,11 @@ RewriteRule   ^/u/<strong>([^/]+)</stron
     <dd>
       This is done via the following ruleset:
 
-<div class="example"><pre>
-# This example is valid in per-directory context only
-RewriteCond %{REQUEST_FILENAME}   <strong>!-s</strong>
+<div class="example"><p><code>
+# This example is valid in per-directory context only<br />
+RewriteCond %{REQUEST_FILENAME}   <strong>!-s</strong><br />
 RewriteRule ^page\.<strong>html</strong>$          page.<strong>cgi</strong>
  [T=application/x-httpd-cgi,L]
-</pre></div>
+</code></p></div>
 
       <p>Here a request for <code>page.html</code> leads to an
       internal run of a corresponding <code>page.cgi</code> if
@@ -159,20 +159,20 @@ RewriteRule ^page\.<strong>html</strong>
       <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>
 
-<div class="example"><pre>
-RewriteEngine on
-RewriteMap lb rnd:/path/to/serverlist.txt
-
+<div class="example"><p><code>
+RewriteEngine on<br />
+RewriteMap lb rnd:/path/to/serverlist.txt<br />
+<br />
 RewriteRule ^/(.*) http://${lb:servers}/$1 [P,L]
-</pre></div>
+</code></p></div>
 
 <p><code>serverlist.txt</code> will contain a list of the servers:</p>
 
-<div class="example"><pre>
-## serverlist.txt
-
-servers one.example.com|two.example.com|three.example.com
-</pre></div>
+<div class="example"><p><code>
+## serverlist.txt<br />
+<br />
+servers one.example.com|two.example.com|three.example.com<br />
+</code></p></div>
 
 <p>If you want one particular server to get more of the load than the
 others, add it more times to the list.</p>
@@ -213,21 +213,21 @@ featureful than anything you can cobble 
       URL causes the 'page' to be refreshed every time it is
       updated on the filesystem.</p>
 
-<div class="example"><pre>
+<div class="example"><p><code>
 RewriteRule   ^(/[uge]/[^/]+/?.*):refresh  /internal/cgi/apache/nph-refresh?f=$1
-</pre></div>
+</code></p></div>
 
       <p>Now when we reference the URL</p>
 
-<div class="example"><pre>
+<div class="example"><p><code>
 /u/foo/bar/page.html:refresh
-</pre></div>
+</code></p></div>
 
       <p>this leads to the internal invocation of the URL</p>
 
-<div class="example"><pre>
+<div class="example"><p><code>
 /internal/cgi/apache/nph-refresh?f=/u/foo/bar/page.html
-</pre></div>
+</code></p></div>
 
       <p>The only missing part is the NPH-CGI script. Although
       one would usually say "left as an exercise to the reader"
@@ -364,10 +364,10 @@ exit(0);
       <p>We use the following ruleset to expand the tilde URLs
       into the above layout.</p>
 
-<div class="example"><pre>
-RewriteEngine on
+<div class="example"><p><code>
+RewriteEngine on<br />
 RewriteRule   ^/~(<strong>([a-z])</strong>[a-z0-9]+)(.*)  /home/<strong>$2</strong>/$1/public_html$3
-</pre></div>
+</code></p></div>
     </dd>
   </dl>
 
@@ -423,13 +423,13 @@ RewriteRule   ^/~(<strong>([a-z])</stron
       <code>&gt;STRING</code> and <code>=STRING</code> we can
       do time-dependent redirects:</p>
 
-<div class="example"><pre>
-RewriteEngine on
-RewriteCond   %{TIME_HOUR}%{TIME_MIN} &gt;0700
-RewriteCond   %{TIME_HOUR}%{TIME_MIN} &lt;1900
-RewriteRule   ^foo\.html$             foo.day.html [L]
+<div class="example"><p><code>
+RewriteEngine on<br />
+RewriteCond   %{TIME_HOUR}%{TIME_MIN} &gt;0700<br />
+RewriteCond   %{TIME_HOUR}%{TIME_MIN} &lt;1900<br />
+RewriteRule   ^foo\.html$             foo.day.html [L]<br />
 RewriteRule   ^foo\.html$             foo.night.html
-</pre></div>
+</code></p></div>
 
       <p>This provides the content of <code>foo.day.html</code>
       under the URL <code>foo.html</code> from
@@ -468,17 +468,17 @@ RewriteRule   ^foo\.html$             fo
     <dd>
       <p>Use the [E] flag to set an environment variable.</p>
 
-<div class="example"><pre>
-RewriteEngine on
+<div class="example"><p><code>
+RewriteEngine on<br />
 RewriteRule   ^/horse/(.*)   /pony/$1 [E=<strong>rewritten:1</strong>]
-</pre></div>
+</code></p></div>
 
     <p>Later in your ruleset you might check for this environment
     variable using a RewriteCond:</p>
 
-<div class="example"><pre>
+<div class="example"><p><code>
 RewriteCond %{ENV:rewritten} =1
-</pre></div>
+</code></p></div>
 
     </dd>
   </dl>

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=1059175&r1=1059174&r2=1059175&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/rewrite/proxy.html.en (original)
+++ httpd/httpd/trunk/docs/manual/rewrite/proxy.html.en Fri Jan 14 21:18:27 2011
@@ -53,24 +53,24 @@ 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>
 
-<div class="example"><pre>
-RewriteEngine  on
-RewriteBase    /products/
-RewriteRule    ^<strong>widget/</strong>(.*)$  <strong>http://product.example.com/widget/</strong>$1
 [<strong>P</strong>]
+<div class="example"><p><code>
+RewriteEngine  on<br />
+RewriteBase    /products/<br />
+RewriteRule    ^<strong>widget/</strong>(.*)$  <strong>http://product.example.com/widget/</strong>$1
 [<strong>P</strong>]<br />
 ProxyPassReverse /products/widget/ http://product.example.com/widget/
-</pre></div>
+</code></p></div>
 
    <p>In the second example, we proxy the request only if we can't find
    the resource locally. This can be very useful when you're migrating
    from one server to another, and you're not sure if all the content
    has been migrated yet.</p>
 
-<div class="example"><pre>
-RewriteCond %{REQUEST_FILENAME}       <strong>!-f</strong>
-RewriteCond %{REQUEST_FILENAME}       <strong>!-d</strong>
-RewriteRule ^/(.*) http://<strong>old</strong>.example.com$1 [<strong>P</strong>]
+<div class="example"><p><code>
+RewriteCond %{REQUEST_FILENAME}       <strong>!-f</strong><br />
+RewriteCond %{REQUEST_FILENAME}       <strong>!-d</strong><br />
+RewriteRule ^/(.*) http://<strong>old</strong>.example.com$1 [<strong>P</strong>]<br
/>
 ProxyPassReverse / http://old.example.com/
-</pre></div>
+</code></p></div>
     </dd>
 
     <dt>Discussion:</dt>

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=1059175&r1=1059174&r2=1059175&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/rewrite/remapping.html.en (original)
+++ httpd/httpd/trunk/docs/manual/rewrite/remapping.html.en Fri Jan 14 21:18:27 2011
@@ -71,10 +71,10 @@ configuration.</div>
       <p>We rewrite the old URL to the new one internally via the
       following rule:</p>
 
-<div class="example"><pre>
-RewriteEngine  on
+<div class="example"><p><code>
+RewriteEngine  on<br />
 RewriteRule    ^<strong>/old</strong>\.html$  <strong>/new</strong>.html
[PT]
-</pre></div>
+</code></p></div>
     </dd>
   </dl>
 
@@ -102,10 +102,10 @@ RewriteRule    ^<strong>/old</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>
 
-<div class="example"><pre>
-RewriteEngine  on
+<div class="example"><p><code>
+RewriteEngine  on<br />
 RewriteRule    ^<strong>/foo</strong>\.html$  <strong>bar</strong>.html
 [<strong>R</strong>]
-</pre></div>
+</code></p></div>
 </dd>
 
 <dt>Discussion</dt>
@@ -144,18 +144,18 @@ RewriteRule    ^<strong>/foo</strong>\.h
       to the new server, but you might also consider using the Redirect
       or RedirectMatch directive.</p>
 
-<div class="example"><h3>With mod_rewrite</h3><pre>
-RewriteEngine on
+<div class="example"><h3>With mod_rewrite</h3><p><code>
+RewriteEngine on<br />
 RewriteRule   ^/docs/(.+)  http://new.example.com/docs/$1  [R,L]
-</pre></div>
+</code></p></div>
 
-<div class="example"><h3>With RedirectMatch</h3><pre>
+<div class="example"><h3>With RedirectMatch</h3><p><code>
 RedirectMatch ^/docs/(.*) http://new.example.com/docs/$1
-</pre></div>
+</code></p></div>
 
-<div class="example"><h3>With Redirect</h3><pre>
+<div class="example"><h3>With Redirect</h3><p><code>
 Redirect /docs/ http://new.example.com/docs/
-</pre></div>
+</code></p></div>
     </dd>
   </dl>
 
@@ -185,11 +185,11 @@ Redirect /docs/ http://new.example.com/d
       internally leads to the invocation of
       <code>/~quux/foo.cgi</code>.</p>
 
-<div class="example"><pre>
-RewriteEngine  on
-RewriteBase    /~quux/
+<div class="example"><p><code>
+RewriteEngine  on<br />
+RewriteBase    /~quux/<br />
 RewriteRule    ^foo\.<strong>html</strong>$  foo.<strong>cgi</strong>
 [H=<strong>cgi-script</strong>]
-</pre></div>
+</code></p></div>
     </dd>
   </dl>
 
@@ -216,19 +216,21 @@ RewriteRule    ^foo\.<strong>html</stron
       existence of the new extension. If it exists, we take
       that name, else we rewrite the URL to its original state.</p>
 
-<div class="example"><pre>
-#   backward compatibility ruleset for
-#   rewriting document.html to document.php
-#   when and only when document.php exists
-&lt;Directory /var/www/htdocs&gt;
-RewriteEngine on
-RewriteBase /var/www/htdocs
-
-RewriteCond $1.php -f
-RewriteCond $1.html !-f
-RewriteRule ^(.*).html$ $1.php
+<div class="example"><p><code>
+#   backward compatibility ruleset for<br />
+#   rewriting document.html to document.php<br />
+#   when and only when document.php exists<br />
+&lt;Directory /var/www/htdocs&gt;<br />
+<span class="indent">
+RewriteEngine on<br />
+RewriteBase /var/www/htdocs<br />
+<br />
+RewriteCond $1.php -f<br />
+RewriteCond $1.html !-f<br />
+RewriteRule ^(.*).html$ $1.php<br />
+</span>
 &lt;/Directory&gt;
-</pre></div>
+</code></p></div>
     </dd>
 
     <dt>Discussion</dt>
@@ -320,19 +322,19 @@ Redirect /admin/ https://www.example.com
 you might use one of the recipes below.</p>
 
 <p>For sites running on a port other than 80:</p>
-<div class="example"><pre>
-RewriteCond %{HTTP_HOST}   !^www\.example\.com [NC]
-RewriteCond %{HTTP_HOST}   !^$
-RewriteCond %{SERVER_PORT} !^80$
+<div class="example"><p><code>
+RewriteCond %{HTTP_HOST}   !^www\.example\.com [NC]<br />
+RewriteCond %{HTTP_HOST}   !^$<br />
+RewriteCond %{SERVER_PORT} !^80$<br />
 RewriteRule ^/?(.*)         http://www.example.com:%{SERVER_PORT}/$1 [L,R,NE]
-</pre></div>
+</code></p></div>
 
 <p>And for a site running on port 80</p>
-<div class="example"><pre>
-RewriteCond %{HTTP_HOST}   !^www\.example\.com [NC]
-RewriteCond %{HTTP_HOST}   !^$
+<div class="example"><p><code>
+RewriteCond %{HTTP_HOST}   !^www\.example\.com [NC]<br />
+RewriteCond %{HTTP_HOST}   !^$<br />
 RewriteRule ^/?(.*)         http://www.example.com/$1 [L,R,NE]
-</pre></div>
+</code></p></div>
 
         <p>
         If you wanted to do this generically for all domain names - that
@@ -341,11 +343,11 @@ RewriteRule ^/?(.*)         http://www.e
         <strong>example.com</strong>, you could use the following
         recipe:</p>
 
-<div class="example"><pre>
-RewriteCond %{HTTP_HOST} !^www\. [NC]
-RewriteCond %{HTTP_HOST} !^$
+<div class="example"><p><code>
+RewriteCond %{HTTP_HOST} !^www\. [NC]<br />
+RewriteCond %{HTTP_HOST} !^$<br />
 RewriteRule ^/?(.*) http://www.%{HTTP_HOST}/$1 [L,R,NE]
-</pre></div>
+</code></p></div>
 
     <p>These rulesets will work either in your main server configuration
     file, or in a <code>.htaccess</code> file placed in the <code class="directive"><a
href="../mod/core.html#documentroot">DocumentRoot</a></code> of the server.</p>
@@ -375,23 +377,23 @@ 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>
 
-<div class="example"><pre>
-RewriteEngine on
-
-#   first try to find it in dir1/...
-#   ...and if found stop and be happy:
-RewriteCond         %{DOCUMENT_ROOT}/<strong>dir1</strong>/%{REQUEST_URI}  -f
-RewriteRule  ^(.+)  %{DOCUMENT_ROOT}/<strong>dir1</strong>/$1  [L]
-
-#   second try to find it in dir2/...
-#   ...and if found stop and be happy:
-RewriteCond         %{DOCUMENT_ROOT}/<strong>dir2</strong>/%{REQUEST_URI}  -f
-RewriteRule  ^(.+)  %{DOCUMENT_ROOT}/<strong>dir2</strong>/$1  [L]
-
-#   else go on for other Alias or ScriptAlias directives,
-#   etc.
+<div class="example"><p><code>
+RewriteEngine on<br />
+<br />
+#   first try to find it in dir1/...<br />
+#   ...and if found stop and be happy:<br />
+RewriteCond         %{DOCUMENT_ROOT}/<strong>dir1</strong>/%{REQUEST_URI}  -f<br
/>
+RewriteRule  ^(.+)  %{DOCUMENT_ROOT}/<strong>dir1</strong>/$1  [L]<br />
+<br />
+#   second try to find it in dir2/...<br />
+#   ...and if found stop and be happy:<br />
+RewriteCond         %{DOCUMENT_ROOT}/<strong>dir2</strong>/%{REQUEST_URI}  -f<br
/>
+RewriteRule  ^(.+)  %{DOCUMENT_ROOT}/<strong>dir2</strong>/$1  [L]<br />
+<br />
+#   else go on for other Alias or ScriptAlias directives,<br />
+#   etc.<br />
 RewriteRule   ^  -  [PT]
-</pre></div>
+</code></p></div>
     </dd>
   </dl>
 
@@ -419,22 +421,22 @@ 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>
 
-<div class="example"><pre>
-HostnameLookups on
-RewriteEngine on
-RewriteMap    multiplex         txt:/path/to/map.mirrors
-RewriteCond  %{REMOTE_HOST}     ([a-z]+)$ [NC]
+<div class="example"><p><code>
+HostnameLookups on<br />
+RewriteEngine on<br />
+RewriteMap    multiplex         txt:/path/to/map.mirrors<br />
+RewriteCond  %{REMOTE_HOST}     ([a-z]+)$ [NC]<br />
 RewriteRule   ^/(.*)$  ${multiplex:<strong>%1</strong>|http://www.example.com/}$1
 [R,L]
-</pre></div>
-
-<div class="example"><pre>
-##  map.mirrors -- Multiplexing Map
+</code></p></div>
 
-de        http://www.example.de/
-uk        http://www.example.uk/
-com       http://www.example.com/
+<div class="example"><p><code>
+##  map.mirrors -- Multiplexing Map<br />
+<br />
+de        http://www.example.de/<br />
+uk        http://www.example.uk/<br />
+com       http://www.example.com/<br />
 ##EOF##
-</pre></div>
+</code></p></div>
     </dd>
 
     <dt>Discussion</dt>
@@ -479,16 +481,16 @@ com       http://www.example.com/
       All other browsers receive page <code>foo.32.html</code>.
       This is done with the following ruleset:</p>
 
-<div class="example"><pre>
-RewriteCond %{HTTP_USER_AGENT}  ^<strong>Mozilla/3</strong>.*
-RewriteRule ^foo\.html$         foo.<strong>NS</strong>.html          [<strong>L</strong>]
-
-RewriteCond %{HTTP_USER_AGENT}  ^<strong>Lynx/</strong>.*         [OR]
-RewriteCond %{HTTP_USER_AGENT}  ^<strong>Mozilla/[12]</strong>.*
-RewriteRule ^foo\.html$         foo.<strong>20</strong>.html          [<strong>L</strong>]
-
+<div class="example"><p><code>
+RewriteCond %{HTTP_USER_AGENT}  ^<strong>Mozilla/3</strong>.*<br />
+RewriteRule ^foo\.html$         foo.<strong>NS</strong>.html          [<strong>L</strong>]<br
/>
+<br />
+RewriteCond %{HTTP_USER_AGENT}  ^<strong>Lynx/</strong>.*         [OR]<br
/>
+RewriteCond %{HTTP_USER_AGENT}  ^<strong>Mozilla/[12]</strong>.*<br />
+RewriteRule ^foo\.html$         foo.<strong>20</strong>.html          [<strong>L</strong>]<br
/>
+<br />
 RewriteRule ^foo\.html$         foo.<strong>32</strong>.html          [<strong>L</strong>]
-</pre></div>
+</code></p></div>
     </dd>
   </dl>
 
@@ -519,9 +521,9 @@ RewriteRule ^foo\.html$         foo.<str
        we replace <code>/puppies</code> and <code>/canines</code>
        by the canonical <code>/dogs</code>.</p>
 
-<div class="example"><pre>
+<div class="example"><p><code>
 RewriteRule   ^/(puppies|canines)/(.*)    /dogs/$2  [R]
-</pre></div>
+</code></p></div>
         </dd>
 
      <dt>Discussion:</dt>
@@ -529,9 +531,9 @@ RewriteRule   ^/(puppies|canines)/(.*)  
      This should really be accomplished with Redirect or RedirectMatch
      directives:
 
-     <div class="example"><pre>
+     <div class="example"><p><code>
      RedirectMatch ^/(puppies|canines)/(.*) /dogs/$2
-     </pre></div>
+     </code></p></div>
      </dd>
       </dl>
 
@@ -560,10 +562,10 @@ using the following ruleset:</p>
       <code>/about/</code>:
       </p>
      
-<div class="example"><pre>
-RewriteEngine on
+<div class="example"><p><code>
+RewriteEngine on<br />
 RewriteRule   <strong>^/$</strong>  /about/  [<strong>R</strong>]
-</pre></div>
+</code></p></div>
 
 <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>
 
@@ -597,32 +599,36 @@ 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>
 
-<div class="example"><pre>
-&lt;Directory /var/www/my_blog&gt;
-  FallbackResource index.php
+<div class="example"><p><code>
+&lt;Directory /var/www/my_blog&gt;<br />
+<span class="indent">
+  FallbackResource index.php<br />
+</span>
 &lt;/Directory&gt;
-</pre></div>
+</code></p></div>
 
 <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>
 
-<div class="example"><pre>
-&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]
+<div class="example"><p><code>
+&lt;Directory /var/www/my_blog&gt;<br />
+<span class="indent">
+  RewriteBase /my_blog<br />
+<br />
+  RewriteCond /var/www/my_blog/%{REQUEST_FILENAME} !-f<br />
+  RewriteCond /var/www/my_blog/%{REQUEST_FILENAME} !-d<br />
+  RewriteRule ^ index.php [PT]<br />
+</span>
 &lt;/Directory&gt;
-</pre></div>
+</code></p></div>
 
 <p>If, on the other hand, you wish to pass the requested URI as a query
 string argument to index.php, you can replace that RewriteRule with:</p>
 
-<div class="example"><pre>
+<div class="example"><p><code>
   RewriteRule (.*) index.php?$1 [PT,QSA]
-</pre></div>
+</code></p></div>
 
 <p>Note that these rulesets can be uses in a <code>.htaccess</code>
 file, as well as in a &lt;Directory&gt; block.</p>

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=1059175&r1=1059174&r2=1059175&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/rewrite/rewritemap.html.en (original)
+++ httpd/httpd/trunk/docs/manual/rewrite/rewritemap.html.en Fri Jan 14 21:18:27 2011
@@ -155,17 +155,17 @@ may be used, and give examples of each.<
     <p>The file <code>/etc/apache2/productmap.txt</code> then contains
     the following:</p>
 
-    <div class="example"><h3>Product to ID map</h3><pre>
-##
-##  productmap.txt - Product to ID map file
-##
-
-television 993
-stereo     198
-fishingrod 043
-basketball 418
+    <div class="example"><h3>Product to ID map</h3><p><code>
+##<br />
+##  productmap.txt - Product to ID map file<br />
+##<br />
+<br />
+television 993<br />
+stereo     198<br />
+fishingrod 043<br />
+basketball 418<br />
 telephone  328
-</pre></div>
+    </code></p></div>
 
     <p>Thus, when <code>http://example.com/product/television</code> is
     requested, the <code>RewriteRule</code> is applied, and the request
@@ -207,14 +207,14 @@ telephone  328
     to one of the servers in the 'static' pool, while everything
     else is sent to one of the 'dynamic' pool.</p>
 
-    <div class="example"><h3>Rewrite map file</h3><pre>
-##
-##  map.txt -- rewriting map
-##
-
-static   www1|www2|www3|www4
+    <div class="example"><h3>Rewrite map file</h3><p><code>
+##<br />
+##  map.txt -- rewriting map<br />
+##<br />
+<br />
+static   www1|www2|www3|www4<br />
 dynamic  www5|www6
-</pre></div>
+    </code></p></div>
 
     <div class="example"><h3>Configuration directives</h3><p><code>
     RewriteMap servers rnd:/path/to/file/map.txt<br />



Mime
View raw message