Re: Forcing URL Rewrite before Proxy pass

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



/U wrote:
Thanks Andre and Jorge. I combined your suggestions to arrive at the following:

       ProxyRequests Off
<Proxy balancer://clusterx>
         BalancerMember http://server:8080/
      </Proxy>

      <VirtualHost *:80>
        Redirect /securehttps://server/secure
       </VirtualHost>

      <VirtualHost *:443>
            ProxyPass /secure balancer://clusterx/
            ProxyPassReverse /secure balancer://clusterx/
            ProxyPreserveHost On
       </VirtualHost>


What happens is that the first mapping works fine:

    http://server/seure/index.html     ==>  https://server/secure/index.html

But the mapping
     https://server/secure/index.html    ==>  http://server:8080

does not work and I get a 404:

    logs# cat ssl_access_log
    10.xx.xx.xx - - [01/Aug/2009:12:43:43 -0700] "GET /secure/index.html
HTTP/1.1" 404 294

I am not so knowledgeable in the Proxy* series of directives, but one idea is that you need to make sure *inside the VirtualHost* that you turn on all the required options.
You show only a snippet, so there is no way to tell.
It is possible that some/all of the Proxy* stuff does not automatically get "inherited" from the "main" part of the configuration (the part that is outside of both <VirtualHost> sections).

To summarise : move any Proxy* directives which may be left outside of <VirtualHost> sections, inside the 2d <VirtualHost> section, and try again.


If you want to know more :

Once you start using <VirtualHost> sections, the way of looking at your configuration and at Apache in general changes :

- whatever is in the "main" section (outside any <VirtualHost>) is read first when Apache starts up, and only sets default values. - what is inside the <VirtualHost> section of the VirtualHost which processes a any given request, overrides these default values, just for the current request. The general case is thus that the main default values are automatically inherited by each VirtualHost. But some specific directives are not. The documentation of these directives usually tells you when that is the case, but they are not always clear about this. In doubt thus, duplicate the directives in each VirtualHost where you want them to apply.






---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
  "   from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx


[Index of Archives]     [Open SSH Users]     [Linux ACPI]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Squid]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux