On Sat, Jul 07, 2012 at 10:01:05AM +0200, Claudio Poli wrote: > Il giorno 07/lug/2012, alle ore 09:42, Willy Tarreau ha scritto: > > [snip] > > Then you really need a proxy, because what you're describing is a proxy. > > There is a "secret" http_proxy option in haproxy, but it will not be > > usable for what you want, as it is only able to parse IP:ports in the > > URI (eg: "GET http://127.0.0.1:5005/ HTTP/1.1"). And I really don't see > > how to combine a header with this. You see, haproxy's goal is to guarantee > > that the traffic cannot come to a host that is not referenced in the conf. > > And you're precisely trying to overcome this, there's too little > > intersection > > between your need and what haproxy is aimed at. > > Hello Willy, > thanks for taking time to reply. > > I totally get your point and you confirmed my suspicions. > Do you, or anyone else on the list, have experience or can suggest a software > to use in this case beside nginx?
You may want to check squid and varnish (maybe). Also, I'm not completely convinced that nginx must absolutely store POST requests. I have memories of the ability to disable this buffering, you might want to check the doc again. Regards, Willy
