http://cbonte.github.io/haproxy-dconv/configuration-1.6.html#4.2-option%20http_proxy
is probably the answer to my question, but does the system's
libresolv() get used to dynamically map name to IP? (no resolvers
list needed?)
http://cbonte.github.io/haproxy-dconv/configuration-1.6.html#5.3.2-res
Hi Sergii,
You can reject requests as soon as you reach a certain amount in the
queue. Check the queue() fetch.
Baptiste
On Wed, Mar 23, 2016 at 1:23 AM, Sergii Mikhtoniuk wrote:
> Thanks for the pointer Baptiste, communicating backend load out-of-band is
> an interesting idea.
>
> Since `agen
a la squid, but w/o caching, and a syntax I'm more comfortable with,
and a resolvers mechanism that can handle AWS ELB elasticity.
http://wiki.squid-cache.org/Features/HTTPS#CONNECT_tunnel
http://gc-taylor.com/blog/2011/11/10/nginx-aws-elb-name-resolution-resolvers
On Tue, Mar 22, 2016 at 11:03 P
I see METH_CONNECT as a pre-defined acl, but much googling leaves me
without a clue as to how to use it.
I hope to have haproxy act as a forward proxy target for browsers
using a proxy.pac file. I believe proxied traffic (both HTTP and
HTTPS) usually goes to the same proxy port, with HTTPS wrappe
Dear Purchase Manager
Nice to me you,i am Ali Wang from Yindu Tools.
If you are going to purchase new order of hydraulic tools,hydraulic pumps,
Hydraulic cylinders,Busbar processor machines,etc for your new year market.
please reply me.
Thanks for the pointer Baptiste, communicating backend load out-of-band is
an interesting idea.
Since `agent-check` can only influence weights, I can see it being useful
in mitigating problems that result in uneven capacity of the backends. For
example if there is a rouge process eating up one cor
Hi Daniel,
Good catch
I propose to return an alert only if the proxy being tested is
frontend or a listen.
There is no way from the backend to know which frontends points to it,
so we can't check if memory will be allocated or not.
Baptiste
On Fri, Mar 18, 2016 at 2:28 PM, Daniel Schneller
On Tue, Mar 22, 2016 at 1:59 AM, Sergii Mikhtoniuk wrote:
> Hi,
>
> My question is more about HTTP/REST in general, but I can't think of a
> better place to find experts than this mailing list.
>
> Can you share your approaches to providing back pressure with HTTP? I'm
> talking about handling cas
On Tue, Mar 22, 2016 at 2:17 PM, Craig McLure wrote:
> Hi,
>
> I'm hoping to experiment with enabling keep-alive on my service, but the
> documentation isn't entirely clear for my use case, the general
> implementation is as follows:
>
> 1) A HTTP request comes in
> 2) A LUA script grabs the reque
On Tue, Mar 22, 2016 at 8:54 PM, Gary Barrueto wrote:
> And how many entries there currently in the cache?
>
> On Tue, Mar 22, 2016 at 12:51 PM, Gary Barrueto wrote:
>>
>> How does one monitor that the ssl cachesize isn't too small or the
>> hit/miss rate? Thanks
>>
>> -gary
>
>
Hi Gary,
Issue
And how many entries there currently in the cache?
On Tue, Mar 22, 2016 at 12:51 PM, Gary Barrueto wrote:
> How does one monitor that the ssl cachesize isn't too small or the
> hit/miss rate? Thanks
>
> -gary
>
How does one monitor that the ssl cachesize isn't too small or the hit/miss
rate? Thanks
-gary
Hello,
I can send your marketing emails to millions of people, for a very better price,
if you want me to send out bulk emails for you to promote your products, please
contact
me today, and i have a special offer for you.
Warm regards,
Alice Wenston
Templating out (or entirely-procedurally-generating) your HAproxy config
file is a must once you exceed the bare minimum of complexity. :-)
Best of luck!
On Tue, Mar 22, 2016 at 3:16 AM, Beluc wrote:
> well, it's can become a real mess with lot of server and source :)
> but sure, it works !
>
>
Hi Larry,
> Hi,
>
> HA-Proxy version 1.5.14
> Ubuntu 15.10
>
> I have had a look in the archives for this problem and it appears a few
> times, but I have an additional worry:
> When we have a number of sequential reloads happening, some old
> processes are left behind.
Please upgrade to
Hi,
HA-Proxy version 1.5.14
Ubuntu 15.10
I have had a look in the archives for this problem and it appears a few
times, but I have an additional worry:
When we have a number of sequential reloads happening, some old processes
are left behind.
This is ok if we have old connections that persist, pr
Hi,
I'm trying to setup a parallel RSA/ECC setup as described here:
http://blog.haproxy.com/2015/07/15/serving-ecc-and-rsa-certificates-on-same-ip-with-haproxy/
but in my case the sample was never captured and thus the ECC backend
has never
been used until I added something else that depends on
Hi,
I'm hoping to experiment with enabling keep-alive on my service, but the
documentation isn't entirely clear for my use case, the general
implementation is as follows:
1) A HTTP request comes in
2) A LUA script grabs the request body, does some analysis on it, and
injects a Cookie: header into
well, it's can become a real mess with lot of server and source :)
but sure, it works !
2016-03-21 19:21 GMT+01:00 James Brown :
> Why not just add each server multiple times with a different src parameter
> and a different name.
>
> Something like
>
> backend my_be
> mode tcp
> server ser
19 matches
Mail list logo
