Hi Àbéjídé,
On 24/07/2018 17:59, Àbéjídé Àyodélé wrote:
> Hi Friends,
>
> I am trying to bump session limits via the maxconn in the global
> section as
> below:
>
> cat /etc/haproxy/redacted-haproxy.cfg
> global
> maxconn 1
> stats socket /var/run/redacted-haproxy-stats.sock user haproxy
> Sorry, that was a "can" that really meant "can't" :) I can't
reproduce it.
Aw well, I was surprised it was so easy :)
> Can you try to upgrade to 1.8.12 ? A number of bugs have been fixed since
I did try the upgrade to 1.8.12, got the same results (segfault)
although I wasn't able to
Hi Julian,
On Tue, Jul 24, 2018 at 12:58:27PM -0400, Julien Semaan wrote:
> Hi Olivier,
>
> Glad you're able to replicate it because I can't get it to happen
> consistently!
> I'd be happy if you could share the details of how it could be replicated if
> that's not too complex or hard to explain
Hi Manu,
On Mon, Jul 23, 2018 at 06:12:34PM +0200, Emmanuel Hocdet wrote:
> Hi Willy,
>
> This patch is necessary to build with current BoringSSL (SSL_SESSION is now
> opaque).
> BoringSSL correctly matches OpenSSL 1.1.0 since 3b2ff028 for haproxy needs.
> The patch revert part of haproxy
Hi Olivier,
Glad you're able to replicate it because I can't get it to happen
consistently!
I'd be happy if you could share the details of how it could be
replicated if that's not too complex or hard to explain via email.
Anyway, attached to this email, you'll find the haproxy configuration
Hi Julian,
On Mon, Jul 23, 2018 at 09:07:32AM -0400, Julien Semaan wrote:
> Hi all,
>
> We're currently using haproxy in our project PacketFence
> (https://packetfence.org) and are currently experiencing an issue with
> haproxy segfaulting when TCP splicing is enabled.
>
> We're currently
Hi Friends,
I am trying to bump session limits via the maxconn in the global section as
below:
cat /etc/haproxy/redacted-haproxy.cfg
global
maxconn 1
stats socket /var/run/redacted-haproxy-stats.sock user haproxy group
haproxy
mode 660 level operator expose-fd listeners
frontend
On Tue, Jul 24, 2018 at 04:59:39PM +0200, Olivier Houchard wrote:
> Right now, when we have "server", "default-server", or "server-template"
> in a frontend, we warn about it being ignored, only to be considered fatal
> later.
> That sounds a bit silly, so the attached patch makes it non-fatal.
Hi,
Right now, when we have "server", "default-server", or "server-template"
in a frontend, we warn about it being ignored, only to be considered fatal
later.
That sounds a bit silly, so the attached patch makes it non-fatal.
Regards,
Olivier
>From 9d2ab5b57dd4d14bce82923cb9b35bb74ac642bb Mon
Hi Milan,
On Tue, Jul 24, 2018 at 12:23:37PM +0200, Milan Petruzelka wrote:
> Hi Willy,
>
> Do you *think* that you got less CLOSE_WAITs or that the latest fixes
> > didn't change anything ? I suspect that for some reason you might be
> > hit by several bugs, which is what has complicated the
Hi Willy,
Do you *think* that you got less CLOSE_WAITs or that the latest fixes
> didn't change anything ? I suspect that for some reason you might be
> hit by several bugs, which is what has complicated the diagnostic, but
> that's just pure guess.
>
>
I'm not sure. I left patched haproxy
Hello
It works with :
> rewrite ^(/.*)\.html https://$host/$1 permanent;
Thank you :)
Envoyé de mon iPhone
> Le 24 juil. 2018 à 08:49, Aleksandar Lazic a écrit :
>
> Hi.
>
>> On 20/07/2018 11:16, -- wrote:
>> Hello,
>>
>> In fact I just want the display of the .html extension on my
Hi.
On 20/07/2018 11:16, -- wrote:
Hello,
In fact I just want the display of the .html extension on my site no longer
displayed
I use haproxy with Nginx, I can make url rewrite with Nginx that works well:
server {
rewrite ^(/.*)\.html(\?.*)?$ $1$2 permanent;
How about to use this in the
On 07/20/2018 12:03 AM, Aleksandar Lazic wrote:
Hi.
On 18/07/2018 13:10, Haim Ari wrote:
Hello,
Trying to set backend by regexp
This regexp works outside of haproxy
String:
/1.0/manage/bu/ca?token=68bf68bf68bf68bf68bf=1212121212=123456789
Regexp:
Hi Julien.
On 23/07/2018 13:59, Julien Semaan wrote:
Doing it with the patch does the equivalent of disabling it with the
option (realized there was an option afterwards).
We're more looking to know if the haproxy team is interested in getting
the issue addressed more than just getting the
15 matches
Mail list logo
