On Fri, Jul 17, 2015 at 10:02:55PM +0200, Baptiste wrote:
> Hi,
>
> The documentation is missing the usesrc requirements about root privileges.
> This patch add this information in the doc.
applied, thank you Baptiste.
Willy
> First would be resolution of SRV records and actually using the port
> supplied by the SRV record as the port for the server. I looked at the code
> and it doesn't seem like too much work, most of it would probably be
> changing the config stuff accordingly.
You're right, this could be an intere
> Actually a local resolver can take care of that for you as well since every
> resolver I know allows configuring a different destination on domain basis.
> Also as described in the first email, the server has to be resolvable via
> the OS resolving stack as well otherwise haproxy won't start.
Th
Hi Robin,
> I don't understand the necessity of the hold valid config option. DNS has
> something that takes care of this for you called the TTL. Besides if hold
> valid is shorter then the TTL it would be kind of pointless since the
> resolvers you are querying won't re-resolve until the TTL expi
On Wed, Jul 15, 2015 at 8:28 AM, Marco Corte wrote:
> Il 14/07/2015 22:11, Baptiste ha scritto:
>>
>> - when parsing the configuration, HAProxy uses libc functions and
>>>
>>> resolvers provided by the operating system => if the server can't be
>>> resolved at this step, then HAProxy can't start
>
Hi Roberto,
Look in your log lines, block 2, HAProxy says "--IN". 'IN' is for
cookie persistence.
'I' means the cookie sent by the client is invalid and 'N' means
HAProxy did not perform any action on persistence.
In such case, you could try to match that there are no prefix in your
cookie and do
On Thu, Jul 16, 2015 at 5:06 PM, Pavlos Parissis
wrote:
>
>
> On 16/07/2015 04:02 μμ, Krishna Kumar (Engineering) wrote:
>> Hi John,
>>
>> Your suggestion works very well, and exactly what I was looking for.
>> Thank you very much.
>>
>
>
> You could also try https://github.com/unixsurfer/haproxy
Hi,
The documentation is missing the usesrc requirements about root privileges.
This patch add this information in the doc.
Baptiste
From 8537d9b6c136a270c79670ebccf972a11fa86af7 Mon Sep 17 00:00:00 2001
From: Baptiste Assmann
Date: Fri, 17 Jul 2015 21:59:42 +0200
Subject: [PATCH] DOC usesrc roo
Hi Nathan,
The 'usesrc' keyword triggers this error. It needs root privileges.
(just checked in the source code)
Baptiste
On Thu, Jul 16, 2015 at 5:13 PM, Nathan Williams wrote:
> oh, i think this comment thread explains it:
> http://comments.gmane.org/gmane.comp.web.haproxy/20366. I'll see ab
Hi Marc,
> Hi all,
>
> I have some problem making ocsp stapling working. here is what i did :
>
> I have 8150.pem with chain, cert and key in it.
>
> I have 8150.pem.ocsp that seems ok :
>
> # openssl ocsp -respin 8150.pem.ocsp -text -CAfile alphassl256.chain
> OCSP Response Data:
> OCSP Respons
> I've problem to rewrite cookie path and cookie domain in HAproxy; I've a
> Nginx configuration but I want to move from Nginx to HAProxy for this proxy
> pass.
Just for my curiosity, why removing nginx ???
> This is a Nginx config I want to replace:
>
> location /~xxx/ {
> proxy_cookie_do
On Wed, Jul 15, 2015 at 1:14 PM, mlist wrote:
>>> Hi,
>>> we see there is a new feature of HAProxy, peer and share table
>>> (sticky-table). This peer feature can be used to have in synch stick cookie
>>> so if one haproxy goes down the other can take over connections ?
>
>
>> Yes, the stick tab
Hi Marc-Antoine,
no idea, sorry.
Maybe some of our SSL experts may help :)
Baptiste
On Wed, Jul 15, 2015 at 11:06 AM, Marc-Antoine
wrote:
> Hi,
>
> nobody knows plz ?
>
> On Thu, 9 Jul 2015 13:06:59 +0200,
> Marc-Antoine wrote :
>
>> Hi all,
>>
>> I have some problem making ocsp stapling work
Hi,
SSL offloading in front of IMAPs (port 993) is supported.
If you try to do STARTTLS over IMAP, it is not supported.
Baptiste
On Wed, Jul 15, 2015 at 10:38 AM, Cohen Galit wrote:
> Hello HAProxy team,
>
>
>
> I see that the SSL offloading for http protocol is already supported (
> http://b
We found this behavior does not appears if we manually clean cookie in the
browser. There is a configuration option to invalidate old cookie so client
does not reuse this strange cookie not recognized by server ?
Roberto
From: mlist
Sent: venerdì 17 luglio 2015 16.19
To: 'haproxy@formilux.or
L’actualité hebdomadaire par RFI - 17/07/2015
Visualisez cet email dans votre navigateur
http://rfi.nlfrancemm.com/HM?b=gQRtBBnUxM7jMDLaCWRqVuORe5TYoPh8BjRdO0cBe62Ucya3KFDdXImPDdyLPgQ6&c=cRDsx-VBZP65aEzWJHLFHg
Ukraine: quand l'ex-président Saakachvili pilote Odessa
L’ex-président géorgien s
Hello,
On 07/14/2015 10:11 PM, Baptiste wrote:
>
> I know the message above is very long, but we really need your feedback!
>
First, many thanks for tackling this! It surely makes many peoples live
much easier. Reading this makes me want two things, one of them being a
little "not-haproxy-like"
We have compiled and installed haproxy version 1.6 dev2.
If we use cookie insert all works, but if we use cookie prefix
(ASP.NET_SessionId) or sticky table in which one have to specify cookie to be
sticked, so using cookie name = ASP.NET_SessionId) we have a strange behavior.
BLOCK1
As you can
Thank you.
I was seeking the document for string `uptime` and `time`, but nothing related
found. how silly :)
> On Jul 17, 2015, at 2:35 PM, Pavlos Parissis
> wrote:
>
>
> On 17/07/2015 06:02 πμ, Ruoshan Huang wrote:
>> hi,
>>I found that the html stats page has a column of status which c
Dear purchasing manager,
Hello,this Klaus from Hangzhou Modern Color Printing Co., Ltd.,our company is a
professional printing manufacturer with years’s experience.so we want to avail
ourselves of opportunity establishing business relation with you.
Please link our company website : http://www.t
20 matches
Mail list logo