Httpd ProxyPass: Difference between revisions
Jump to navigation
Jump to search
(→Syntax) |
|||
| Line 11: | Line 11: | ||
=Overview= | =Overview= | ||
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 | 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: | For ProxyPass-related mod_proxy concepts see: | ||
Revision as of 03:55, 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 ...]
Example
ProxyPass "/something" "http://example.com/something-else
Alternative using <Location>:
<Location "/something">
ProxyPass "http://example.com/something-else"
</Location>
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: