English cleanup to the mod_rewrite documentation although we're in code
freeze state. But we should now really kick out the 1.3.12 baby. We're
already behind the proposed dates...
Submitted by: G.W. Haywood <ged@jubileegroup.co.uk>
Reviewed by: Ralf S. Engelschall
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@84654 13f79535-47bb-0310-9956-ffa450edef68
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>
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@84409 13f79535-47bb-0310-9956-ffa450edef68
Submitted by: Tony Finch <fanf@demon.net>
Reviewed by: Dean, Randy, Jim, Lars, Martin
Obtained from:
Add the new mod_vhost_alias.c modules for better mass-hosting. This
has been used at Demon Internet with excellent results and basically
replaces the "old" method of using mod_rewrite. Big advantage is
that adding new vhosts can be done without restarting the server.
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@83357 13f79535-47bb-0310-9956-ffa450edef68
``nocase|NC'' flag (as RewriteCond already does for ages) to match case
insensitive (this especially avoids nasty patterns like `[tT][eE][sS][tT]').
Second two additional internal map functions `escape' and `unescape' were
added which can be used to escape/unescape to/from hex-encodings in URLs parts
(this is especially useful in combination with map lookups).
Submitted by: Magnus Bodin, Ian Kallen
Integrated and fixed by: Ralf S. Engelschall
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@82563 13f79535-47bb-0310-9956-ffa450edef68
Adding of new information. Now especially the detailed information about how
mod_rewrite internally works which is written down here for better
understanding of the directive documentation. I've also painted two initial
figures to illustrate this better which are added to htdocs/manual/images/.
(Phase 2 will be error correction and markup code cleanup)
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@80404 13f79535-47bb-0310-9956-ffa450edef68
constructs, thus no one noticed that it can be used to lookup the REMOTE_USER
variable (one of the mod_rewrite FAQs) even in per-server context. One just
has to use %{LA-U:REMOTE_USER} instead of %{REMOTE_USER} there. Notice that
%{REMOTE_USER} is also useful, but only for per-dir context.
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@80320 13f79535-47bb-0310-9956-ffa450edef68
Unix derivates who doesn't accept the locking of pipes directly.
But we perhaps have another problem: According to FreeBSD's manpage and a hint
by the submitter of PR#1029 flock() has to be used on opened filedescriptors
which are _not_ duplicated via fork(). This currently is not the case...
Submitted by: Ralf S. Engelschall
Reviewed by: Ralf S. Engelschall, Jim Jagielski
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@80311 13f79535-47bb-0310-9956-ffa450edef68
be used as a Reverse Proxy (where the backend servers are choosen via a `rnd'
map) and to allow mass virtual hosting without <VirtualHost> sections (where
you have to fix the case of server names when translating the Host-Header to a
directory structure).
Together with the comitted ProxyPassReverse directive we now have solved
two things the users have asked in the past:
1. The ability to use Apache as a full-featured Reverse Proxy
2. The ability to do mass virtual hosting without <VirtualHost> sections.
For both topics we should write stand-alone documents (perhaps inside
htdocs/manual/misc/) because they are not trivial to do, even when we now have
the functionality ;-)
Submitted by: Ralf S. Engelschall
Reviewed by: Dean Gaudet, Ralf S. Engelschall
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@80298 13f79535-47bb-0310-9956-ffa450edef68
'i' and 'b' to 'EM' and 'STRONG' respectively. Been threatening
to do this for months.. no-one need try to maintain this when
writing/modifiying the docs.
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@80021 13f79535-47bb-0310-9956-ffa450edef68
First the grouped parts of RewriteRule pattern matches (parenthesis!) can be
accessed now via backreferences $1..$9 in RewriteConds test-against strings in
addition to RewriteRules subst string. Second the grouped parts of RewriteCond
pattern matches (parenthesis!) can be accessed now via backreferences %1..%9
both in following RewriteCond test-against strings and RewriteRules subst
string. This provides maximum flexibility through the use of backreferences.
Additionally the rewriting engine was cleaned up by putting common code to the
new expand_backrefs_inbuffer() function.
Submitted by: Ralf S. Engelschall
Reviewed by: Dean Gaudet, Ralf S. Engelschall
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@78903 13f79535-47bb-0310-9956-ffa450edef68
of ``RewriteCond %{...} !^$'' which is ugly and has
bad performance.
Obtained from:
Submitted by: Ralf S. Engelschall
Reviewed by: Dean Gaudet, Ralf S. Engelschall
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@78852 13f79535-47bb-0310-9956-ffa450edef68
<A NAME> (thanks, Marc). Lots of trailing blanks removed throughout.
Small addition to the new_features_1_3 page. Plenty of
cleanup still to come..
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@78545 13f79535-47bb-0310-9956-ffa450edef68
