Available Languages: en

diff --git a/docs/manual/rewrite/avoid.xml b/docs/manual/rewrite/avoid.xml index 192fe54c0d..7ca79d0518 100644 --- a/docs/manual/rewrite/avoid.xml +++ b/docs/manual/rewrite/avoid.xml @@ -48,8 +48,10 @@ configuration.

mod_rewrite introduction Redirection and remapping Controlling access +Virtual hosts +Proxying Advanced techniques and tricks - + diff --git a/docs/manual/rewrite/proxy.html b/docs/manual/rewrite/proxy.html new file mode 100644 index 0000000000..94eceb093e --- /dev/null +++ b/docs/manual/rewrite/proxy.html @@ -0,0 +1,5 @@ +# GENERATED FROM XML -- DO NOT EDIT + +URI: proxy.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/docs/manual/rewrite/proxy.html.en b/docs/manual/rewrite/proxy.html.en new file mode 100644 index 0000000000..a7a0f69d85 --- /dev/null +++ b/docs/manual/rewrite/proxy.html.en @@ -0,0 +1,93 @@ + + + +Using mod_rewrite for Proxying - Apache HTTP Server + + + + + +

+Apache > HTTP Server > Documentation > Version 2.3 > Rewrite

Using mod_rewrite for Proxying

Available Languages: en

+ + +

This document supplements the mod_rewrite +reference documentation. It describes +how to use the RewriteRule's [P] flag to proxy content to another server. +A number of recipes are provided that describe common scenarios.

+ +

Proxying Content with mod_rewrite

+ + + +

Description:

+ mod_rewrite provides the [P] flag, which allows URLs to be passed, + via mod_proxy, to another server. Two examples are given here. In + one example, a URL is passed directly to another server, and served + as though it were a local URL. In the other example, we proxy + missing content to a back-end server.

Solution:

To simply map a URL to another server, we use the [P] flag, as + follows:

+ +

+RewriteEngine  on
+RewriteBase    /products/
+RewriteRule    ^widget/(.*)$  http://product.example.com/widget/$1  [P]
+ProxyPassReverse /products/widget/ http://product.example.com/widget/
+

+ +

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.

+ +

+RewriteCond %{REQUEST_FILENAME}       !-f
+RewriteCond %{REQUEST_FILENAME}       !-d
+RewriteRule ^/(.*) http://old.example.com$1 [P]
+ProxyPassReverse / http://old.example.com/
+

Discussion:

In each case, we add a ProxyPassReverse directive to ensure + that any redirects issued by the backend are correctly passed on to + the client.

+ +

Consider using either ProxyPass or ProxyPassMatch whenever possible in + preference to mod_rewrite.

+ +

Available Languages: en

+ \ No newline at end of file diff --git a/docs/manual/rewrite/proxy.xml b/docs/manual/rewrite/proxy.xml new file mode 100644 index 0000000000..8e59531b25 --- /dev/null +++ b/docs/manual/rewrite/proxy.xml @@ -0,0 +1,103 @@ + + + + + + + + + Rewrite + +Using mod_rewrite for Proxying + +

+ +

This document supplements the mod_rewrite +reference documentation. It describes +how to use the RewriteRule's [P] flag to proxy content to another server. +A number of recipes are provided that describe common scenarios.

+ +

+Module documentation +mod_rewrite introduction +Redirection and remapping +Controlling access +Virtual hosts + +Advanced techniques and tricks +When not to use mod_rewrite + +

+ + Proxying Content with mod_rewrite + +

Description:

Solution:

To simply map a URL to another server, we use the [P] flag, as + follows:

+ +

+RewriteEngine  on
+RewriteBase    /products/
+RewriteRule    ^widget/(.*)$  http://product.example.com/widget/$1  [P]
+ProxyPassReverse /products/widget/ http://product.example.com/widget/
+

+ +

+RewriteCond %{REQUEST_FILENAME}       !-f
+RewriteCond %{REQUEST_FILENAME}       !-d
+RewriteRule ^/(.*) http://old.example.com$1 [P]
+ProxyPassReverse / http://old.example.com/
+

Discussion:

In each case, we add a ProxyPassReverse directive to ensure + that any redirects issued by the backend are correctly passed on to + the client.

+ +

Consider using either ProxyPass or ProxyPassMatch whenever possible in + preference to mod_rewrite.

+ +

+ + diff --git a/docs/manual/rewrite/proxy.xml.meta b/docs/manual/rewrite/proxy.xml.meta new file mode 100644 index 0000000000..d71d22d39a --- /dev/null +++ b/docs/manual/rewrite/proxy.xml.meta @@ -0,0 +1,12 @@ + + + + + proxy + /rewrite/ + .. + + + en + + diff --git a/docs/manual/rewrite/remapping.html.en b/docs/manual/rewrite/remapping.html.en index 6ef1e53fca..87e6a20c20 100644 --- a/docs/manual/rewrite/remapping.html.en +++ b/docs/manual/rewrite/remapping.html.en @@ -48,8 +48,7 @@ configuration.

Proxying Content with mod_rewrite

- - - -

Description:

- mod_rewrite provides the [P] flag, which allows URLs to be passed, - via mod_proxy, to another server. Two examples are given here. In - one example, a URL is passed directly to another server, and served - as though it were a local URL. In the other example, we proxy - missing content to a back-end server.

Solution:

To simply map a URL to another server, we use the [P] flag, as - follows:

- -

-RewriteEngine  on
-RewriteBase    /products/
-RewriteRule    ^widget/(.*)$  http://product.example.com/widget/$1  [P]
-ProxyPassReverse /products/widget/ http://product.example.com/widget/
-

- -

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.

- -

-RewriteCond %{REQUEST_FILENAME}       !-f
-RewriteCond %{REQUEST_FILENAME}       !-d
-RewriteRule ^/(.*) http://old.example.com$1 [P]
-ProxyPassReverse / http://old.example.com/
-

Discussion:

In each case, we add a ProxyPassReverse directive to ensure - that any redirects issued by the backend are correctly passed on to - the client.

- -

Consider using either ProxyPass or ProxyPassMatch whenever possible in - preference to mod_rewrite.

Available Languages: en

diff --git a/docs/manual/rewrite/remapping.xml b/docs/manual/rewrite/remapping.xml index 8e87235019..c91ca97f1c 100644 --- a/docs/manual/rewrite/remapping.xml +++ b/docs/manual/rewrite/remapping.xml @@ -41,8 +41,10 @@ configuration. Module documentation mod_rewrite introduction - + Controlling access +Virtual hosts +Proxying Advanced techniques and tricks When not to use mod_rewrite @@ -664,62 +666,4 @@ file, as well as in a <Directory> block.

- - Proxying Content with mod_rewrite - -

Description:

Solution:

To simply map a URL to another server, we use the [P] flag, as - follows:

- -

-RewriteEngine  on
-RewriteBase    /products/
-RewriteRule    ^widget/(.*)$  http://product.example.com/widget/$1  [P]
-ProxyPassReverse /products/widget/ http://product.example.com/widget/
-

- -

-RewriteCond %{REQUEST_FILENAME}       !-f
-RewriteCond %{REQUEST_FILENAME}       !-d
-RewriteRule ^/(.*) http://old.example.com$1 [P]
-ProxyPassReverse / http://old.example.com/
-

Discussion:

In each case, we add a ProxyPassReverse directive to ensure - that any redirects issued by the backend are correctly passed on to - the client.

- -

Consider using either ProxyPass or ProxyPassMatch whenever possible in - preference to mod_rewrite.

- -

- diff --git a/docs/manual/rewrite/vhosts.html b/docs/manual/rewrite/vhosts.html new file mode 100644 index 0000000000..b99209bdf6 --- /dev/null +++ b/docs/manual/rewrite/vhosts.html @@ -0,0 +1,5 @@ +# GENERATED FROM XML -- DO NOT EDIT + +URI: vhosts.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/docs/manual/rewrite/vhosts.html.en b/docs/manual/rewrite/vhosts.html.en new file mode 100644 index 0000000000..98e664574a --- /dev/null +++ b/docs/manual/rewrite/vhosts.html.en @@ -0,0 +1,42 @@ + + + +Using mod_rewrite for virtual hosting - Apache HTTP Server + + + + + +

+Apache > HTTP Server > Documentation > Version 2.3 > Rewrite

Using mod_rewrite for virtual hosting

Available Languages: en

+ + +

This document supplements the mod_rewrite +reference documentation. It describes +how you can use mod_rewrite to create dynamically +configured virtual hosts.

+ +

mod_rewrite is not the best way to configure +virtual hosts. You should first consider the alternatives before resorting to +mod_rewrite.

+ +

See also

See also

Forbidding Image "Hotlinking"

See also

See also

URL-based sharding accross multiple backends

See also

See also

Using mod_rewrite for Proxying

See also

Proxying Content with mod_rewrite

See also

See also

From Old to New (internal)

Proxying Content with mod_rewrite

Using mod_rewrite for virtual hosting

See also