You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by "Ralf S. Engelschall" <rs...@apache.org> on 1998/07/25 14:16:38 UTC
cvs commit: apache-1.3/htdocs/manual/mod mod_rewrite.html
rse 98/07/25 05:16:38
Modified: src CHANGES
htdocs/manual/mod mod_rewrite.html
Log:
Update the mod_rewrite.html document to correctly reflect the situation of the
`proxy' (`[P]') feature.
PR: 2679
Revision Changes Path
1.986 +3 -0 apache-1.3/src/CHANGES
Index: CHANGES
===================================================================
RCS file: /export/home/cvs/apache-1.3/src/CHANGES,v
retrieving revision 1.985
retrieving revision 1.986
diff -u -r1.985 -r1.986
--- CHANGES 1998/07/25 11:56:28 1.985
+++ CHANGES 1998/07/25 12:16:35 1.986
@@ -1,4 +1,7 @@
Changes with Apache 1.3.2
+
+ *) Update the mod_rewrite.html document to correctly reflect the situation
+ of the `proxy' (`[P]') feature. [Ralf S. Engelschall] PR#2679
*) Fix `install-includes' sub-target of `install' target in top-level
Makefile.tmpl: The umask+cp approach didn't work as expected (especially
1.33 +13 -11 apache-1.3/htdocs/manual/mod/mod_rewrite.html
Index: mod_rewrite.html
===================================================================
RCS file: /export/home/cvs/apache-1.3/htdocs/manual/mod/mod_rewrite.html,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -r1.32 -r1.33
--- mod_rewrite.html 1998/06/22 09:48:38 1.32
+++ mod_rewrite.html 1998/07/25 12:16:37 1.33
@@ -1493,18 +1493,20 @@
<LI>'<STRONG><CODE>proxy|P</CODE></STRONG>' (force <STRONG>p</STRONG>roxy)<BR>
This flag forces the substitution part to be internally forced as a proxy
request and immediately (i.e. rewriting rule processing stops here) put
- through the proxy module. You have to make sure that the substitution
- string is a valid URI (e.g. typically <CODE>http://</CODE>) which can
- be handled by the Apache proxy module. If not you get an error from
- the proxy module. Use this flag to achieve a more powerful implementation
- of the <CODE>mod_proxy</CODE> directive <CODE>ProxyPass</CODE>, to map
- some remote stuff into the namespace of the local server.
+ through the <A HREF="mod_proxy.html">proxy module</A>. You have to make
+ sure that the substitution string is a valid URI (e.g. typically starting
+ with <CODE>http://</CODE><EM>hostname</EM>) which can be handled by the
+ Apache proxy module. If not you get an error from the proxy module. Use
+ this flag to achieve a more powerful implementation of the <A
+ HREF="mod_proxy.html#proxypass">ProxyPass</A> directive, to map some
+ remote stuff into the namespace of the local server.
<P>
- Notice: <STRONG>You really have to put <CODE>ProxyRequests On</CODE> into your
- server configuration to prevent proxy requests from leading to core-dumps
- inside the Apache kernel. If you have not compiled in the proxy module,
- then there is no core-dump problem, because mod_rewrite checks for
- existence of the proxy module and if lost forbids proxy URLs. </STRONG>
+ Notice: To use this functionality make sure you have the proxy module
+ compiled into your Apache server program. If you don't know please check
+ whether <CODE>mod_proxy.c</CODE> is part of the ``<CODE>httpd -l</CODE>''
+ output. If yes, this functionality is available to mod_rewrite. If not,
+ then you first have to rebuild the ``<CODE>httpd</CODE>'' program with
+ mod_proxy enabled.
<P>
<LI>'<STRONG><CODE>last|L</CODE></STRONG>' (<STRONG>l</STRONG>ast rule)<BR>
Stop the rewriting process here and