https://issues.apache.org/bugzilla/show_bug.cgi?id=53947

          Priority: P2
            Bug ID: 53947
          Assignee: [email protected]
           Summary: Feature Request, RewriteRule - ProxyPreserveHost flag
                    (and related)
          Severity: normal
    Classification: Unclassified
                OS: Linux
          Reporter: [email protected]
          Hardware: PC
            Status: NEW
           Version: 2.5-HEAD
         Component: mod_rewrite
           Product: Apache httpd-2

Hi
- ProxyPreserveHost is a server conf directive only, and in my opinion, a must
have feature for in all cluster & lb related proxy configuration.
- RewriteRule [P] is a very usefull directive for migrating a specific part of
an application to another server

- There should be very little depency between a cluster IP and a service name
(domain name) - that's the whole purpose  of ProxyPreserveHost

In massive name base virtualhost environnement, i have only ONE virtualhost
<Virtualhost>
  ServerAlias allalloweddomains.tld
  VirtualDocumentRoot /etc/httpd/redirector/%0
</VirtualHost>

I cannot enable ProxyPreserveHost on the whole Virtualhost (location /services/
is irrelevant).

I'm asking for 
* enabling ProxyPreserveHost in .htaccess ? [OR]
* creating an inline ProxyPreserveHost RewriteRule flag

Therefore, the
RewriteCond %QUERY_STRING ClassName=SpecificSOAPWSClass
RewriteCond (.*)  http:// [cluster ip with upcomming architecture evolution]/$1
[P,PPH]

Would work as supposed.
New apache extensions mod_remoteip are (kindeof) around same kind of proxy/lb
transparency issue.


In the same spirit, ProxyImposeHost might also be usefull
RewriteCond (.*)  http:// [cluster ip with upcomming architecture evolution]/$1
[P,PIH=newfeature.domain.com]

I hope you'll agree with this new feature.

Best Regards.

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to