Httpd ProxyPass: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 12: | Line 12: | ||
The ProxyPass directive maps remote servers into the local server URL-space, by creating a [[Httpd_mod_proxy_Concepts#Workers|worker]] that handles the request associated with the declared remote URL. A (more flexible) alternative is the use of RewriteRule with the [P] flag. | The ProxyPass directive maps remote servers into the local server URL-space, by creating a [[Httpd_mod_proxy_Concepts#Workers|worker]] that handles the request associated with the declared remote URL. A (more flexible) alternative is the use of RewriteRule with the [P] flag. | ||
For ProxyPass-related mod_proxy concepts see: | |||
<blockquote style="background-color: #f9f9f9; border: solid thin lightgrey;"> | |||
:[[Httpd_mod_proxy_Concepts#The_ProxyPass_Directive|ProxyPass Concepts]] | |||
</blockquote> | |||
=Syntax= | =Syntax= | ||
Revision as of 00:47, 23 December 2016
External
Internal
Overview
The ProxyPass directive maps remote servers into the local server URL-space, by creating a worker that handles the request associated with the declared remote URL. A (more flexible) alternative is the use of RewriteRule with the [P] flag.
For ProxyPass-related mod_proxy concepts see:
Syntax
ProxyPass [path] !|url [key=value ...]
Order
ProxyPass and ProxyPassMatch rules are checked in the order in which they were specified in the configuration file, and the first rule match wins.
Also see: