Re: [users@httpd] wildcard in proxypass logic

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

 



I appreaciate the responses; though I'm still having problems. I believe I
have a workaround -- by changing the order of the URL from
"/product/service/" to "/service/product" and implementing the wildcard
logic on the tomcat side, I believe I can achive the same effect. I still
don't understand why the former approach doesn't work. Can someone explain
why the first <Location> tag will proxy the request to tomcat, but the
latter <Location> tag will ignore the ProxyPass directive and try to serve
up the file from apache?

> <Location "/product1/services/">
> Order Allow,Deny
> Allow from all
> ProxyPass                 http://poduct1-tomcat:8080/web-app/services/
> ProxyPassReverse       /
> </Location>

> <Location ~ "/product1/services/">
> Order Allow,Deny
> Allow from all
> ProxyPass                 http://poduct1-tomcat:8080/web-app/services/
> ProxyPassReverse       /
> </Location>




----- Original Message ----- 
From: "Steven Wagner" <swagner@xxxxxxxx>
To: <users@xxxxxxxxxxxxxxxx>
Sent: Thursday, February 16, 2006 9:48 AM
Subject: Re: [users@httpd] wildcard in proxypass logic


> Hello Oliver,
>
> Thanks for the reply. If I try to define an expression (either
LocationMatch
> or using ~ in Location), rather than the 403 Forbidden error I get a 404
Not
> Found error. It's as if the ProxyPass directive is lost and Apache tries
to
> process the request locally.
>
> <LocationMatch "/*/services/">
> Order Allow,Deny
> Allow from all
> ProxyPass                 http://default-tomcat:8080/web-app/services/
> ProxyPassReverse       /
> </LocationMatch>
>
> ----- Original Message ----- 
> From: <Oliver.Schaudt@xxxxxxxxx>
> To: <users@xxxxxxxxxxxxxxxx>
> Sent: Thursday, February 16, 2006 2:13 AM
> Subject: AW: [users@httpd] wildcard in proxypass logic
>
>
> For the wildcard use better "LocationMatch" instead of "Location".
> http://httpd.apache.org/docs/2.2/en/mod/core.html#locationmatch
>
> If you want to playing with a bunch of tomcats in the back you should have
a
> look of mod_proxy_balancer/mod_proxy_ajp too
> http://httpd.apache.org/docs/2.2/en/mod/mod_proxy_balancer.html
>
>
> Bye
> Oliver
>
> -----Ursprüngliche Nachricht-----
> Von: Steven Wagner [mailto:swagner@xxxxxxxx]
> Gesendet: Do 16.02.2006 00:43
> An: users@xxxxxxxxxxxxxxxx
> Betreff: [users@httpd] wildcard in proxypass logic
>
> Hello, I'm new to this list and apologize if my protocol is incorrect. I'm
> trying to set up proxy using wildcards. The apache is being used as a
front
> end security layer to a pool of tomcat servers. The idea is to provide a
> means to route different product server requests to different tomcat
servers
> pools, where the more popular products would have bigger pools. But since
> there could potentially be a large number of product (most of which would
> not be that popular), we wanted to have a default tomcat pool, hence the
use
> of the wildcard. So with the following httpd.conf settings requests for
> product1/services and product2/services are proxied correctly, but
requests
> for product3/services return a 403 Forbidden error, where as I would have
> thought it would be handled by the wild card entry. Any insight to the
> problem or alternative solutions are appreciated. Thanks.
>
> <Location /product1/services/>
> Order Allow,Deny
> Allow from all
> ProxyPass                 http://poduct1-tomcat:8080/web-app/services/
> ProxyPassReverse       /
> </Location>
>
> <Location /product2/services/>
> Order Allow,Deny
> Allow from all
> ProxyPass                 http://poduct2-tomcat:8080/web-app/services/
> ProxyPassReverse       /
> </Location><Location /*/services/>
> Order Allow,Deny
> Allow from all
> ProxyPass                 http://default-tomcat:8080/web-app/services/
> ProxyPassReverse       /
> </Location>
>
>
>
>
>
>
> --------------------------------------------------------------------------
--
> ----
>
>
> > ---------------------------------------------------------------------
> > 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
>
>
>
> ---------------------------------------------------------------------
> 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
>
>



---------------------------------------------------------------------
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