Bug 54309 - clarification on the <Location> directive when used with proxy request
Summary: clarification on the <Location> directive when used with proxy request
Status: NEW
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: Documentation (show other bugs)
Version: 2.4-HEAD
Hardware: All All
: P2 trivial (vote)
Target Milestone: ---
Assignee: HTTP Server Documentation List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-12-15 20:51 UTC by Christoph Anton Mitterer
Modified: 2012-12-15 20:51 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christoph Anton Mitterer 2012-12-15 20:51:03 UTC
Hi.

The documentation of the <Location> directive (https://httpd.apache.org/docs/trunk/en/mod/core.html#location) tells about how it changes when used with proxy requests:
"For all origin (non-proxy) requests, the URL to be matched is a URL-path of the form /path/. No scheme, hostname, port, or query string may be included. For proxy requests, the URL to be matched is of the form scheme://servername/path, and you must include the prefix."

I think two things should be clarified here:

1) As far as I can see,... the above does not apply when using a reverse proxy...
i.e. only with forward proxies, the prefix of schema/domain must be added, right?


2) Not sure whether this is possible at all:
Can I have a location which apply to both, proxied and non-proxied content? If so, how is it determined, which Location sections apply?


Cheers,
Chris.