14:12:44 -0500
Jeffrey E Burgoyne burgo...@keenuh.com wrote:
If people feel this is a worthwhile addition to the main code base,
please
let me know and I'll pass it back.
Not sure I follow exactly what you've added.
How big a patch is your change? If it's not too big to admit
easy
No pain, I wanted something simple so people can decide if the concept is
worth having. I figured that if I require it, eventually some else
eventually will as well :
ht01b07:~/apacheConfig/tarball/httpd-2.2.14/modules/proxy # diff -u
mod_proxy.h mod_proxy.h.real
--- mod_proxy.h 2011-02-24
as opposed to
Location
/cgi-bin http://otherserver.com/cgi-bin
/Location
So I just went with that style.
On Wed, Feb 23, 2011 at 7:12 PM, Jeffrey E Burgoyne burgo...@keenuh.com
wrote:
I am doing some work with a large organization that has recently
acquired
two products that work
Sorry, should have read it closer, change my example to :
Location /cgi-bin
ProxyPass http://otherserver.com/cgi-bin
/Location
So I just went with that style.
On Wed, Feb 23, 2011 at 7:12 PM, Jeffrey E Burgoyne
burgo...@keenuh.com
wrote:
I am doing some work with a large
I agree I like that better.
Implementation looks more in-depth than the work I've done before, I'll
have a look at it sometime if no one else wishes to take it up.
Well, that style would be to have an option to ProxyPass that flips
the worker's preserve host attribute, eg:
ProxyPass
I am doing some work with a large organization that has recently acquired
two products that work properly through a reverse proxy system only when
ProxyPreserveHost is set to on.
The organization had issue as they are mandated to have only a single
hostname as a point of entry for their web
Quite small, only took a few hours to do. I'll post it tomorrow.
Basically it does the same as PreserveProxyHost except it works on a URL
basis, not on a per virtual host basis.
On Wed, 23 Feb 2011 14:12:44 -0500
Jeffrey E Burgoyne burgo...@keenuh.com wrote:
If people feel
4 - 1 compression ratio is fine unless you are serving lots of rich
content, which generally will see no performance gain if not reduced
performance.
As pointed out this option is not a one size fits all arrangement.
Shouldn't the default be the best config for everyone based upon the
lowest
I am not using the apache balancing, but using a network level load
balancer, but this concept may apply. We append an HTTP header on output
that tells you which machine you were on. As long as each machine has a
separate config file of some sort (in our setup it is http.conf unique per
machine,
