Re: Support for ProxyPreserveHost with mod_proxy_balancer?

2006-02-13 Thread Graham Leggett

Gregor J. Rothfuss wrote:

i am trying to use mod_proxy_balancer with a backend that is in turn 
using name-based virtual hosts.


it seems that mod_proxy_balancer doesn't honor ProxyPreserveHost (both 
2.2.0 and trunk), and does not send the Host: header to the backend.


would there be interest in a patch for that or am i attempting something 
dumb?


The Host header should always be sent to the backend, not doing so 
violates HTTP/1.1. This sounds like a bug of some kind.


Regards,
Graham
--


smime.p7s
Description: S/MIME Cryptographic Signature


AW: Support for ProxyPreserveHost with mod_proxy_balancer?

2006-02-13 Thread Plüm , Rüdiger , VIS


 -Ursprüngliche Nachricht-
 Von: Graham Leggett 
 
 Gregor J. Rothfuss wrote:
 
  i am trying to use mod_proxy_balancer with a backend that is in turn
  using name-based virtual hosts.
  
  it seems that mod_proxy_balancer doesn't honor 
 ProxyPreserveHost (both
  2.2.0 and trunk), and does not send the Host: header to the backend.
  
  would there be interest in a patch for that or am i attempting 
  something
  dumb?
 
 The Host header should always be sent to the backend, not doing so 
 violates HTTP/1.1. This sounds like a bug of some kind.

This is not the problem. A host header *is* sent to the backend, but
it is the *wrong* one (the hostname of the worker I assume and not
the hostname of the reverse proxy).

Regards

Rüdiger



AW: Support for ProxyPreserveHost with mod_proxy_balancer?

2006-02-13 Thread Plüm , Rüdiger , VIS


 -Ursprüngliche Nachricht-
 Von: Gregor J. Rothfuss 
 
 
 hi,
 
 i am trying to use mod_proxy_balancer with a backend that is in turn 
 using name-based virtual hosts.
 
 it seems that mod_proxy_balancer doesn't honor 
 ProxyPreserveHost (both 
 2.2.0 and trunk), and does not send the Host: header to the backend.

After a first quick view in the code on trunk I cannot see a problem there.
Can you please post your config here, such that we can rule out a config
problem?

Furthermore could you please open a bug in bugzilla for this? This makes
things easier to track and to reference.


Regards

Rüdiger


Re: AW: Support for ProxyPreserveHost with mod_proxy_balancer?

2006-02-13 Thread Gregor J. Rothfuss

Plüm wrote:


After a first quick view in the code on trunk I cannot see a problem there.
Can you please post your config here, such that we can rule out a config
problem?


let me know if this snip is enough:

NameVirtualHost *:8080
ProxyRequests Off
ProxyPreserveHost On

Proxy balancer://tiles_live_cluster/
   BalancerMember 192.168.1.54:8080
   BalancerMember 192.168.1.55:8080
   BalancerMember 192.168.1.56:8080
   BalancerMember 192.168.1.57:8080
   BalancerMember 192.168.1.58:8080
   BalancerMember 192.168.1.59:8080
   BalancerMember 192.168.1.60:8080
   BalancerMember 192.168.1.61:8080
   BalancerMember 192.168.1.62:8080
   BalancerMember 192.168.1.63:8080
/Proxy

#
# VirtualHost example:
# Almost any Apache directive may go into a VirtualHost container.
# The first VirtualHost section is used for all requests that do not
# match a ServerName or ServerAlias in any VirtualHost block.
#
VirtualHost *:8080
ServerName t0.tiles.com
ServerAlias t1.tiles.com
ServerAlias t2.tiles.com
ServerAlias t3.tiles.com

ProxyPreserveHost On
ProxyPass / balancer://tiles_live_cluster/ nofailover=On
ProxyPassReverse / balancer://tiles_live_cluster/
/VirtualHost

Proxy balancer://live_cluster
   BalancerMember 192.168.1.54:8080
   BalancerMember 192.168.1.55:8080
   BalancerMember 192.168.1.56:8080
   BalancerMember 192.168.1.57:8080
   BalancerMember 192.168.1.58:8080
   BalancerMember 192.168.1.59:8080
   BalancerMember 192.168.1.60:8080
   BalancerMember 192.168.1.61:8080
   BalancerMember 192.168.1.62:8080
   BalancerMember 192.168.1.63:8080
/Proxy

VirtualHost *:8080
ServerName customer.server.com
ServerAlias tiles.server.com
ServerAlias tiles0.server.com
ServerAlias tiles1.server.com
ServerAlias tiles2.server.com
ServerAlias tiles3.server.com

ProxyPreserveHost On
ProxyPass / balancer://live_cluster/ nofailover=On
ProxyPassReverse / balancer://live_cluster/
/VirtualHost



Furthermore could you please open a bug in bugzilla for this? This makes
things easier to track and to reference.


will do if it is not a PEBKAC issue (problem exists between keyboard and 
chair) ;)


--
http://43folders.com/2005/09/19/writing-sensible-email-messages/


Re: Support for ProxyPreserveHost with mod_proxy_balancer?

2006-02-13 Thread Jim Jagielski

I can't recreate that here... Can you provide more info?

On Feb 13, 2006, at 12:43 AM, Gregor J. Rothfuss wrote:


hi,

i am trying to use mod_proxy_balancer with a backend that is in  
turn using name-based virtual hosts.


it seems that mod_proxy_balancer doesn't honor ProxyPreserveHost  
(both 2.2.0 and trunk), and does not send the Host: header to the  
backend.


would there be interest in a patch for that or am i attempting  
something dumb?


thanks,

-gregor





Re: AW: Support for ProxyPreserveHost with mod_proxy_balancer?

2006-02-13 Thread Joost de Heer

ProxyPassReverse / balancer://tiles_live_cluster/


This looks wrong, shouldn't this be http://reverse.proxy.host/ ?

Joost


Re: AW: Support for ProxyPreserveHost with mod_proxy_balancer?

2006-02-13 Thread Ruediger Pluem


On 02/13/2006 06:31 PM, Joost de Heer wrote:
 ProxyPassReverse / balancer://tiles_live_cluster/
 
 
 This looks wrong, shouldn't this be http://reverse.proxy.host/ ?

Yes, this also looks wrong to me. I think he needs a separate ProxyPassReverse
line for *each* of the backend servers he configured in the cluster.
The balancer://tiles_live_cluster/ is not used any longer once an appropriate
worker has been chosen from the cluster.

Regards

Rüdiger


Support for ProxyPreserveHost with mod_proxy_balancer?

2006-02-12 Thread Gregor J. Rothfuss

hi,

i am trying to use mod_proxy_balancer with a backend that is in turn 
using name-based virtual hosts.


it seems that mod_proxy_balancer doesn't honor ProxyPreserveHost (both 
2.2.0 and trunk), and does not send the Host: header to the backend.


would there be interest in a patch for that or am i attempting something 
dumb?


thanks,

-gregor