Hi,
In order to be able to process layer 7 manipulation (what you want to
achieve) for *each* request, then you must enable http mode on your
frontebd/backend and to enable the option http-server-close.
cheers
On Thu, Oct 27, 2011 at 12:21 AM, Vivek Malik wrote:
> The documentation also says
>
The documentation also says
In HTTP mode, it is possible to rewrite, add or delete some of the request and
response headers based on regular expressions. It is also possible to block a
request or a response if a particular header matches a regular expression,
which is enough to stop most elementar
OoO En cette nuit nuageuse du jeudi 27 octobre 2011, vers 00:02, Vivek
Malik disait :
> We have been using haproxy in production for around 6 months while
> using httpclose. We use functions like reqidel, reqadd to manipulate
> request headers and use_backend to route a request to a specific
>
We have been using haproxy in production for around 6 months while using
httpclose. We use functions like reqidel, reqadd to manipulate request
headers and use_backend to route a request to a specific backend.
We run websites which often have ajax calls and load javascripts and css
files from the
Our session service deals with persistence... Our application is written
in such a way that it does not matter the backend it is connected to
(i.e. we do not need HAProxy to keep the persistence). Currently,
HAProxy is set to Round-Robbin (default).
Also of note, in the lab, we are only conne
Hi,
how do you achieve session persistance in HAProxy configuration?
What load-balancing algorithm do you use?
Can you configure HAProxy to log your session cookie then show us some
log lines?
cheers
On Wed, Oct 26, 2011 at 2:57 PM, Sean Patronis wrote:
>
>
> We are in the process of converti
We are in the process of converting most of our HAProxy usage to be http
balanced (instead of TCP).
In our lab we are using stunnel to decrypt our https traffic to http
which then gets piped to haproxy. We also have a load balanced session
service that stunnel/HAProxy also serves which uses us
I can appreciate having to keep a slow application layer highly available
via long timeouts, but as a suggestion:
a) keep lots of available sockets open and think about the "timeout wait"
sysctl reuse/recycle variables
And
b) think about creating a simple page (in whatever language and environme
8 matches
Mail list logo