cvs commit: apache-1.3/htdocs/manual/misc rewriteguide.html

[rse]

rse 00/02/11 00:58:29

  Modified:htdocs/manual/misc rewriteguide.html
  Log:
  Change /a to /A to be consistent with remaining layout.
  Thanks to Martin for hint.
  
  Revision  ChangesPath
  1.7   +5 -5  apache-1.3/htdocs/manual/misc/rewriteguide.html
  
  Index: rewriteguide.html
  ===
  RCS file: /home/cvs/apache-1.3/htdocs/manual/misc/rewriteguide.html,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- rewriteguide.html 2000/02/10 16:53:00 1.6
  +++ rewriteguide.html 2000/02/11 08:58:28 1.7
  @@ -29,13 +29,13 @@
   
   P
   This document supplements the mod_rewrite A
  -HREF=../mod/mod_rewrite.htmlreference documentation/a. It describes
  +HREF=../mod/mod_rewrite.htmlreference documentation/A. It describes
   how one can use Apache's mod_rewrite to solve typical URL-based problems
   webmasters are usually confronted with in practice. I give detailed
   descriptions on how to solve each problem by configuring URL rewriting
   rulesets.
   
  -H2A name=ToC1Introduction to mod_rewrite/a/H2
  +H2A name=ToC1Introduction to mod_rewrite/A/H2
   
   The Apache module mod_rewrite is a killer one, i.e. it is a really
   sophisticated module which provides a powerful way to do URL manipulations.
  @@ -50,7 +50,7 @@
   of its power. This paper tries to give you a few initial success events to
   avoid the first case by presenting already invented solutions to you.
   
  -H2A name=ToC2Practical Solutions/a/H2
  +H2A name=ToC2Practical Solutions/A/H2
   
   Here come a lot of practical solutions I've either invented myself or
   collected from other peoples solutions in the past. Feel free to learn the
  @@ -724,7 +724,7 @@
   DTSTRONGDescription:/STRONG
   DD
   Do you know the great CPAN (Comprehensive Perl Archive Network) under A
  -HREF=http://www.perl.com/CPAN;http://www.perl.com/CPAN/a? This does a
  +HREF=http://www.perl.com/CPAN;http://www.perl.com/CPAN/A? This does a
   redirect to one of several FTP servers around the world which carry a CPAN
   mirror and is approximately near the location of the requesting client.
   Actually this can be called an FTP access multiplexing service. While CPAN
  @@ -1084,7 +1084,7 @@
   P
   A sophisticated DNS-based method for load-balancing is to use the program
   CODElbnamed/CODE which can be found at A
  
-HREF=http://www.stanford.edu/~schemers/docs/lbnamed/lbnamed.html;http://www.stanford.edu/~schemers/docs/lbnamed/lbnamed.html/a.
  
+HREF=http://www.stanford.edu/~schemers/docs/lbnamed/lbnamed.html;http://www.stanford.edu/~schemers/docs/lbnamed/lbnamed.html/A.
   It is a Perl 5 program in conjunction with auxilliary tools which provides a
   real load-balancing for DNS.
   
  
  
  

cvs commit: apache-1.3/htdocs/manual/misc rewriteguide.html

[rse]

rse 00/02/10 08:24:28

  Modified:htdocs/manual/misc rewriteguide.html
  Log:
  Fix typos.
  
  Submitted by: Howard Jones [EMAIL PROTECTED]
  PR: 5733
  
  Revision  ChangesPath
  1.2   +2 -2  apache-1.3/htdocs/manual/misc/rewriteguide.html
  
  Index: rewriteguide.html
  ===
  RCS file: /home/cvs/apache-1.3/htdocs/manual/misc/rewriteguide.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- rewriteguide.html 2000/01/08 14:50:14 1.1
  +++ rewriteguide.html 2000/02/10 16:24:26 1.2
  @@ -1378,7 +1378,7 @@
   DTSTRONGDescription:/STRONG
   DD
   Here comes a really esoteric feature: Dynamically generated but statically
  -served pages, i.e. pages should be delivered as pur static pages (read from
  +served pages, i.e. pages should be delivered as pure static pages (read from
   the filesystem and just passed through), but they have to be generated
   dynamically by the webserver if missing. This way you can have CGI-generated
   pages which are statically unless one (or a cronjob) removes the static
  @@ -1391,7 +1391,7 @@
   
   PTABLE BGCOLOR=#E0E5F5 BORDER=0 CELLSPACING=0 
CELLPADDING=5TRTDPRE
   RewriteCond %{REQUEST_FILENAME}   b!-s/b
  -RewriteCond ^page\.bhtml/b$  page.bcgi/b   
[T=application/x-httpd-cgi,L]
  +RewriteRule ^page\.bhtml/b$  page.bcgi/b   
[T=application/x-httpd-cgi,L]
   /PRE/TD/TR/TABLE
   
   P
  
  
  

cvs commit: apache-1.3/htdocs/manual/misc rewriteguide.html

[rse]

rse 00/02/10 08:35:50

  Modified:htdocs/manual/misc rewriteguide.html
  Log:
  Cleanup my old physical HTML markup into a logical one to
  fit better into the Apache documentation.
  
  Revision  ChangesPath
  1.3   +179 -179  apache-1.3/htdocs/manual/misc/rewriteguide.html
  
  Index: rewriteguide.html
  ===
  RCS file: /home/cvs/apache-1.3/htdocs/manual/misc/rewriteguide.html,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- rewriteguide.html 2000/02/10 16:24:26 1.2
  +++ rewriteguide.html 2000/02/10 16:35:48 1.3
  @@ -28,14 +28,14 @@
   /DIV
   
   P
  -This document supplements the mod_rewrite a
  -href=../mod/mod_rewrite.htmlreference documentation/a. It describes
  +This document supplements the mod_rewrite A
  +HREF=../mod/mod_rewrite.htmlreference documentation/a. It describes
   how one can use Apache's mod_rewrite to solve typical URL-based problems
   webmasters are usually confronted with in practice. I give detailed
   descriptions on how to solve each problem by configuring URL rewriting
   rulesets.
   
  -H2a name=ToC1Introduction to mod_rewrite/a/H2
  +H2A name=ToC1Introduction to mod_rewrite/a/H2
   
   The Apache module mod_rewrite is a killer one, i.e. it is a really
   sophisticated module which provides a powerful way to do URL manipulations.
  @@ -50,7 +50,7 @@
   of its power. This paper tries to give you a few initial success events to
   avoid the first case by presenting already invented solutions to you.
   
  -H2a name=ToC2Practical Solutions/a/H2
  +H2A name=ToC2Practical Solutions/a/H2
   
   Here come a lot of practical solutions I've either invented myself or
   collected from other peoples solutions in the past. Feel free to learn the
  @@ -60,7 +60,7 @@
   ATTENTION: Depending on your server-configuration it can be necessary to
   slightly change the examples for your situation, e.g. adding the [PT] flag
   when additionally using mod_alias and mod_userdir, etc. Or rewriting a 
ruleset
  -to fit in tt.htaccess/tt context instead of per-server context. Always 
try
  +to fit in CODE.htaccess/CODE context instead of per-server context. 
Always try
   to understand what a particular ruleset really does before you use it. It
   avoid problems.
   
  @@ -83,12 +83,12 @@
   DD
   We do an external HTTP redirect for all non-canonical URLs to fix them in the
   location view of the Browser and for all subsequent requests. In the example
  -ruleset below we replace tt/~user/tt by the canonical tt/u/user/tt 
and
  -fix a missing trailing slash for tt/u/user/tt.
  +ruleset below we replace CODE/~user/CODE by the canonical 
CODE/u/user/CODE and
  +fix a missing trailing slash for CODE/u/user/CODE.
   
   PTABLE BGCOLOR=#E0E5F5 BORDER=0 CELLSPACING=0 
CELLPADDING=5TRTDPRE
  -RewriteRule   ^/b~/b([^/]+)/?(.*)/bu/b/$1/$2  [bR/b]
  -RewriteRule   ^/([uge])/(b[^/]+/b)$  /$1/$2b//b   [bR/b]
  +RewriteRule   ^/STRONG~/STRONG([^/]+)/?(.*)/STRONGu/STRONG/$1/$2 
 [STRONGR/STRONG]
  +RewriteRule   ^/([uge])/(STRONG[^/]+/STRONG)$  /$1/$2STRONG//STRONG  
 [STRONGR/STRONG]
   /PRE/TD/TR/TABLE
   
   /DL
  @@ -126,26 +126,26 @@
   DTSTRONGDescription:/STRONG
   DD
   Usually the DocumentRoot of the webserver directly relates to the URL
  -``tt//tt''. But often this data is not really of top-level priority, it 
is
  +``CODE//CODE''. But often this data is not really of top-level priority, 
it is
   perhaps just one entity of a lot of data pools. For instance at our Intranet
  -sites there are tt/e/www//tt (the homepage for WWW), tt/e/sww//tt 
(the
  +sites there are CODE/e/www//CODE (the homepage for WWW), 
CODE/e/sww//CODE (the
   homepage for the Intranet) etc. Now because the data of the DocumentRoot 
stays
  -at tt/e/www//tt we had to make sure that all inlined images and other
  +at CODE/e/www//CODE we had to make sure that all inlined images and other
   stuff inside this data pool work for subsequent requests. 
   
   P
   DTSTRONGSolution:/STRONG
   DD
  -We just redirect the URL tt//tt to tt/e/www//tt.  While is seems
  +We just redirect the URL CODE//CODE to CODE/e/www//CODE.  While is 
seems
   trivial it is actually trivial with mod_rewrite, only.  Because the typical
  -old mechanisms of URL iAliases/i (as provides by mod_alias and friends)
  -only used iprefix/i matching. With this you cannot do such a redirection
  +old mechanisms of URL EMAliases/EM (as provides by mod_alias and friends)
  +only used EMprefix/EM matching. With this you cannot do such a 
redirection
   because the DocumentRoot is a prefix of all URLs. With mod_rewrite it is
   really trivial:
   
   PTABLE BGCOLOR=#E0E5F5 BORDER=0 CELLSPACING=0 
CELLPADDING=5TRTDPRE
   RewriteEngine on
  -RewriteRule   b^/$/b  /e/www/  [bR/b]
  +RewriteRule   STRONG^/$/STRONG  /e/www/  [STRONGR/STRONG]
   /PRE/TD/TR/TABLE
   
   /DL
  @@ -159,9 +159,9 @@
   DD
   Every webmaster can sing a song about the 

cvs commit: apache-1.3/htdocs/manual/misc rewriteguide.html

[rse]

rse 00/02/10 08:38:58

  Modified:htdocs/manual/misc rewriteguide.html
  Log:
  Update old net.sw entry to avoid confusion by the reader.
  
  Revision  ChangesPath
  1.4   +5 -6  apache-1.3/htdocs/manual/misc/rewriteguide.html
  
  Index: rewriteguide.html
  ===
  RCS file: /home/cvs/apache-1.3/htdocs/manual/misc/rewriteguide.html,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- rewriteguide.html 2000/02/10 16:35:48 1.3
  +++ rewriteguide.html 2000/02/10 16:38:57 1.4
  @@ -354,14 +354,13 @@
   drwxrwxr-x  10 netsw  users512 Jul  9 14:08 X11/
   /PREP
   
  -In July 1996 I decided to make this 350 MB archive public to the world via a
  -nice Web interface (A HREF=http://net.sw.engelschall.com/net.sw/;CODE
  -http://net.sw.engelschall.com/net.sw//CODE/a). Nice means that I 
wanted to
  -offer a interface where you can browse directly through the archive 
hierarchy.
  +In July 1996 I decided to make this archive public to the world via a
  +nice Web interface. Nice means that I wanted to
  +offer an interface where you can browse directly through the archive 
hierarchy.
   And nice means that I didn't wanted to change anything inside this 
hierarchy
   - not even by putting some CGI scripts at the top of it.  Why? Because the
   above structure should be later accessible via FTP as well, and I didn't
  -want any Web or CGI stuuf to be there.
  +want any Web or CGI stuff to be there.
   
   P
   DTSTRONGSolution:/STRONG
  @@ -390,7 +389,7 @@
   real STRONGEMnet.sw/EM/STRONG stuff and gets automatically updated 
via
   CODErdist/CODE from time to time. 
   
  - The second part of the problem remains: how to link these two structures
  +The second part of the problem remains: how to link these two structures
   together into one smooth-looking URL tree? We want to hide the 
CODEDATA//CODE
   directory from the user while running the appropriate CGI scripts for the
   various URLs. 
  
  
  

cvs commit: apache-1.3/htdocs/manual/misc rewriteguide.html

[rse]

rse 00/02/10 08:44:06

  Modified:htdocs/manual/misc rewriteguide.html
  Log:
  Make sure we don't receive another PR where a user tried to take the
  solutions exactly as written down without noticing that they usually
  always have to be adjusted for local contexts.
  
  Revision  ChangesPath
  1.5   +2 -0  apache-1.3/htdocs/manual/misc/rewriteguide.html
  
  Index: rewriteguide.html
  ===
  RCS file: /home/cvs/apache-1.3/htdocs/manual/misc/rewriteguide.html,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- rewriteguide.html 2000/02/10 16:38:57 1.4
  +++ rewriteguide.html 2000/02/10 16:43:57 1.5
  @@ -57,12 +57,14 @@
   black magic of URL rewriting from these examples.
   
   P
  +TABLE BGCOLOR=#FFE0E0 BORDER=0 CELLSPACING=0 CELLPADDING=5TRTD
   ATTENTION: Depending on your server-configuration it can be necessary to
   slightly change the examples for your situation, e.g. adding the [PT] flag
   when additionally using mod_alias and mod_userdir, etc. Or rewriting a 
ruleset
   to fit in CODE.htaccess/CODE context instead of per-server context. 
Always try
   to understand what a particular ruleset really does before you use it. It
   avoid problems.
  +/TD/TR/TABLE
   
   H1URL Layout/H1
   
  
  
  

cvs commit: apache-1.3/htdocs/manual/misc rewriteguide.html

[rse]

rse 00/02/10 08:53:08

  Modified:htdocs/manual/misc rewriteguide.html
  Log:
  One more fix. Thanks to Eric Cholet [EMAIL PROTECTED]
  
  Revision  ChangesPath
  1.6   +1 -1  apache-1.3/htdocs/manual/misc/rewriteguide.html
  
  Index: rewriteguide.html
  ===
  RCS file: /home/cvs/apache-1.3/htdocs/manual/misc/rewriteguide.html,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- rewriteguide.html 2000/02/10 16:43:57 1.5
  +++ rewriteguide.html 2000/02/10 16:53:00 1.6
  @@ -1382,7 +1382,7 @@
   served pages, i.e. pages should be delivered as pure static pages (read from
   the filesystem and just passed through), but they have to be generated
   dynamically by the webserver if missing. This way you can have CGI-generated
  -pages which are statically unless one (or a cronjob) removes the static
  +pages which are statically served unless one (or a cronjob) removes the 
static
   contents. Then the contents gets refreshed.
   
   P
  
  
  

cvs commit: apache-1.3/htdocs/manual/misc rewriteguide.html

[rse]

rse 00/01/08 06:50:16

  Modified:src  CHANGES
   htdocs/manual index.html
   htdocs/manual/mod mod_rewrite.html
  Added:   htdocs/manual/misc rewriteguide.html
  Log:
  Make our nitpicking and complaining guys happy:
  
  Added the mod_rewrite `URL Rewriting Guide' to the online documentation
  (htdocs/manual/misc/rewriteguide.html). This paper provides a large
  collection of practical solutions to URL based problems a webmaster is
  often confronted with.
  
  This version of the text was translated from my WML source on my website
  and my old official version is now discarded. So, as it was requested,
  this can be treated as an official donation of this text to the ASF.
  This way the ASF is now the official owner of this text.
  
 - - -
  
  IRONIC
  Be happy and give Ken and Jim the credit for achieving this by being
  such sensitive and friendly to other developers like me and always
  reminding us that it is such contemptuous to implicitly promote ones
  name by writing free software and contributing to projects like Apache.
  Sorry that I have forgotten to donate this piece of text to the ASF in
  the past and instead added such a contemptible hyperlink directing to a
  page on www.engelschall.com. I hope this is now fixed and the closed and
  holy ASF world is rescued again.
  /IRONIC
  
  PERSONAL
  I think, I don't have to say that I'm more than angry and disappointed
  how developers like me are constantly bashed in the ASF... we can go for
  it also in the future, but we should stop looking astonished all the
  time if we find out that too less people contribute to the ASF and old
  developers like me no longer have a warm feeling here, please. It's our
  own fault in thinking that contributions are for free and anonymous just
  because our project is a group effort.
  
  IMHO we already have forgotten the golden rule of Open Source
  development: if one wants happy and long-term contributing developers
  one especially has to make sure they receive the requested credit.
  There is an upper limit a project can accept to give, of course. But
  credit always has to depend on the amount, quality _and_ duration of
  contribution and IMHO cannot be judged by stating that just all people
  are equal and so some contributors can be bashed for the fact that their
  name occurs more often.
  
  It is correct that my name occurs more often caused by the fact that I
  always try to bring in my stuff to the project. But keep in mind that
  this is because I _HAVE_ stuff to bring in which I've created _OUTSIDE_
  the project. So I think its unfair to bash me just because I try harder
  to bring in my additional stuff. If a developer has not much externally
  created stuff, he cannot bring it in to the project, of course. But just
  because one has more externally created stuff and tries to bring it in,
  is IMHO no reason and excuse to bash him for this. It's not my fault
  that I write in my freetime more Open Source packages like most of you.
  
  So if you dislike stuff developers want to bring in, decide on the
  contribution based on fair technical arguments (pros and cons). But
  don't judge the contributions all the time just because you think this
  way you promote someone (be it RSE, GNU or whoever else). Hell, an
  Open Source project is not a group of people to rule their own closed
  world and be celebrated in the press for this. It's still an effort to
  create the best piece of _software_ money can't buy. So you should stop
  thinking about contributors as our enemy. They are the main driving
  force of every project, although some people seem to not understand
  this at all. And whatever you think about my personal opinion, but
  IMHO it's not bad for a project if someone's name is promoted with
  it, too. What is actually bad are those complains and discussions
  which make developers angry and the fact that they result in even less
  contributions.
  /PERSONAL
  
  Revision  ChangesPath
  1.1489+6 -0  apache-1.3/src/CHANGES
  
  Index: CHANGES
  ===
  RCS file: /home/cvs/apache-1.3/src/CHANGES,v
  retrieving revision 1.1488
  retrieving revision 1.1489
  diff -u -r1.1488 -r1.1489
  --- CHANGES   2000/01/01 17:07:32 1.1488
  +++ CHANGES   2000/01/08 14:50:05 1.1489
  @@ -1,5 +1,11 @@
   Changes with Apache 1.3.10
   
  +  *) Added the mod_rewrite `URL Rewriting Guide' to the online
  + documentation (htdocs/manual/misc/rewriteguide.html). This paper
  + provides a large collection of practical solutions to URL based
  + problems a webmaster is often confronted with.
  + [Ralf S. Engelschall]
  +
 *) Add a suexec status report to the '-l' (compiled-in modules)
output. [Ken Coar]
   
  
  
  
  1.30  +1 -0  apache-1.3/htdocs/manual/index.html
  
  Index: index.html