Re[2]: The case for changing the documentation syntax

It sounds like restructuredText and Asciidoc are the top choices. They both look capable: http://hyperpolyglot.org/lightweight-markup I can, as a next step, post this as an Issue on the Github project and it can be triaged and tracked. For something like this, it might even make sense to

Re: Re[2]: The case for changing the documentation syntax

And for comparison's sake, here's Asciidoc renders on github: https://github.com/asciidoctor/asciidoctor/blob/master/README.adoc Other features of the asciidoc/asciidoctor ecosystem are: - Asciidoc is also standardized - https://antora.org/ allows you to build 1 documentation website, from

Re[2]: The case for changing the documentation syntax

I found this page on Github. It uses reStructuredText and demonstrates how Github would render various elements out of the box. Of course, it can be made more visually appealing with other tools, but it's a free benefit that it renders on Github.

Re: Re[2]: The case for changing the documentation syntax

Adding my 2 cents here: I write documentation a lot and would like to mention the Asciidoc format, and more specifically asciidoctor ( https://asciidoctor.org/). Asciidoc is a _very_ powerful syntax yet extremely simple to use. Here's a link to their cheat sheet to give you a quick idea of the

Re[2]: The case for changing the documentation syntax

Yes, either reStructuredText or Markdown would be okay. They both have a very intuitive syntax, so newcomers would pick it up and become productive with it quickly. It is quite easy to learn either one. -- Original Message -- From: "Aleksandar Lazic" To: "Nick Ramirez" ;

Re[2]: agent-check requires newline in response?

Yep, your suggestion reads better to me. -- Original Message -- From: "Willy Tarreau" To: "Nick Ramirez" Cc: haproxy@formilux.org Sent: 12/15/2018 10:30:58 AM Subject: Re: agent-check requires newline in response? Hi Nick, On Fri, Dec 14, 2018 at 05:43:49PM +, Nick Ramirez

Re[2]: HTTP/2 to backend server fails health check when 'option httpchk' set

Thanks! That points me in the right direction. I found that to enable Layer 7 health checks in this case, I would open another port on the web server that does not advertise HTTP/2 support (ALPN HTTP/1.1) or does not use TLS (which also turns off HTTP/2 in the case of the Caddy web server),

Re[2]: [PATCH] MINOR: introduce proxy-v2-options for send-proxy-v2

Hi Manu. -- Originalnachricht -- Von: "Emmanuel Hocdet" An: "Aleksandar Lazic" Cc: "haproxy" Gesendet: 05.02.2018 14:58:20 Betreff: Re: [PATCH] MINOR: introduce proxy-v2-options for send-proxy-v2 Hi Aleks, Le 2 févr. 2018 à

Re[2]: [PATCH] Minor : Add a sampler to extract the microsecond information of the hit date

Thanks for your answer. Interesting use case. Regards aleks -- Originalnachricht -- Von: "Etienne Carrière" An: "Aleksandar Lazic" Cc: haproxy@formilux.org Gesendet: 17.01.2018 23:28:40 Betreff: Re: [PATCH] Minor : Add a sampler to

Re[2]: How to parse custom PROXY protocol v2 header for custom routing in HAProxy configuration?

Hi. Follow up question to proxy protocol Is it possible to handle the Type-Length-Value (TLV) fields in from pp2 in haproxy config or in lua? I refer to 2.2.7. Reserved type ranges https://www.haproxy.org/download/1.8/doc/proxy-protocol.txt from the question on so

Re[2]: [BUG] 100% cpu on each threads

-- Originalnachricht -- Von: "Willy Tarreau" An: "Emmanuel Hocdet" Cc: "haproxy" Gesendet: 12.01.2018 13:04:02 Betreff: Re: [BUG] 100% cpu on each threads On Fri, Jan 12, 2018 at 12:01:15PM +0100, Emmanuel Hocdet wrote: When

Re: Re[2]: Makefile:813: recipe for target 'haproxy' failed

Hi Aleks I have solved the problem, OpenSSL was not recognized TARGET=linux24 USE_OPENSSL=1.1.0g SSL_INC=$STATICLIBSSL/include SSL_LIB=$STATICLIBSSL/lib ADDLIB=-ldl All the best Milenko On 7 January 2018 at 20:25, Aleksandar Lazic wrote: > Zadravo Milenko. > > Please

Re[2]: Makefile:813: recipe for target 'haproxy' failed

Zadravo Milenko. Please keep the list in the communication, thank you very much. -- Originalnachricht -- Von: "Milenko Markovic" An: "Aleksandar Lazic" Gesendet: 07.01.2018 09:02:56 Betreff: Re: Makefile:813: recipe for target 'haproxy'

Re[2]: haproxy without balancing

Hi Angelo. -- Originalnachricht -- Von: "Angelo Hongens" An: "Aleksandar Lazic" ; haproxy@formilux.org Gesendet: 06.01.2018 18:20:47 Betreff: Re: haproxy without balancing Hey Aleksandar, On 05-01-2018 22:05, Aleksandar Lazic wrote: We run a lot

Re[2]: haproxy-1.8 in Fedora

Hi. -- Originalnachricht -- Von: "Ryan O'Hara" An: "Aleksandar Lazic" Cc: haproxy@formilux.org Gesendet: 05.01.2018 23:35:10 Betreff: Re: haproxy-1.8 in Fedora On Fri, Jan 5, 2018 at 3:12 PM, Aleksandar Lazic wrote: Hi

Re[2]: haproxy without balancing

Hi Angelo. -- Originalnachricht -- Von: "Angelo Hongens" An: haproxy@formilux.org Gesendet: 05.01.2018 11:49:55 Betreff: Re: haproxy without balancing On 05-01-2018 11:28, Johan Hendriks wrote: Secondly we could use a single ip and use ACL to route the traffic to

Re[2]: Poll: haproxy 1.4 support ?

-- Originalnachricht -- Von: "Marco Corte" An: haproxy@formilux.org Gesendet: 03.01.2018 13:20:31 Betreff: Re: Poll: haproxy 1.4 support ? Hello. My vote to drop support for version 1.4 +1 .marcoc regards Aleks

Re: Re[2]: CI/CD HAProxy

2017-12-15 13:07 GMT+05:00 Aleksandar Lazic : > Hi > > -- Originalnachricht -- > Von: "Илья Шипицин" > An: "Aleksandar Lazic" > Cc: "Olivier Doucet" ; "HAProxy" < > haproxy@formilux.org> > Gesendet:

Re[2]: CI/CD HAProxy

Hi -- Originalnachricht -- Von: "Илья Шипицин" An: "Aleksandar Lazic" Cc: "Olivier Doucet" ; "HAProxy" Gesendet: 14.12.2017 14:57:29 Betreff: Re: CI/CD HAProxy 2017-09-16 20:01 GMT+05:00

Re[2]: Use haproxy 1.8.x to balance web applications only reachable through Internet proxy

Hi. -- Originalnachricht -- Von: "Moemen MHEDHBI" An: "Gbg" ; haproxy@formilux.org Gesendet: 11.12.2017 18:45:16 Betreff: Re: Use haproxy 1.8.x to balance web applications only reachable through Internet proxy On 11/12/2017 17:21, Gbg wrote:

Re[2]: [ANNOUNCE] haproxy-1.8.0

Hi Willy. -- Originalnachricht -- Von: "Willy Tarreau" An: "Aleksandar Lazic" Cc: haproxy@formilux.org Gesendet: 27.11.2017 23:54:31 Betreff: Re: [ANNOUNCE] haproxy-1.8.0 Hi Aleks, On Mon, Nov 27, 2017 at 09:18:35PM +, Aleksandar Lazic wrote: >

Re[2]: [ANNOUNCE] haproxy-1.8-rc1 : the last mile

Hi. -- Originalnachricht -- Von: "Willy Tarreau" An: "Cyril Bonté" Cc: haproxy@formilux.org Gesendet: 01.11.2017 07:44:23 Betreff: Re: [ANNOUNCE] haproxy-1.8-rc1 : the last mile Hi Cyril, On Wed, Nov 01, 2017 at 01:03:42AM +0100, Cyril Bonté wrote:

Re[2]: Tcp logging in haproxy

Hi -- Originalnachricht -- Von: "kushal bhattacharya" An: haproxy@formilux.org Gesendet: 27.10.2017 12:47:37 Betreff: Re: Tcp logging in haproxy Sorry if it is generated as a new topic i am attaching my configuration until now below On UDP

Re[2]: Multiple Monitor-net

Thank you! Worked perfectly! [Bryan] -- Original Message -- From: "Willy Tarreau" To: "Bryan Rodriguez" Cc: haproxy@formilux.org Sent: 10/16/2015 10:28:13 AM Subject: Re: Multiple Monitor-net On Fri, Oct 16, 2015 at 05:18:24PM +, Bryan

Re[2]: Multiple Monitor-net

What about TCP requests or not HTTP traffic? It seems TCP traffic is still logged when using: http-request set-log-level silent if { src -f aws-checks.list } [Bryan] -- Original Message -- From: "Willy Tarreau" To: "Bryan Rodriguez" Cc:

Re: 2 services (frontend+backend), both with cookies, failure

Hi, On Sat, Oct 11, Kari Mattsson wrote: this got repeated for 50+ times when refreshing on Chrome browser. Then to Firefox.. Oct 11 20:25:17 localhost haproxy[5179]: 10.6.159.238:4248 [11/Oct/2014:20:25:14.300] service_1_outside_80 service_1_inside/App_101 3264/0/0/1/+3265 200 +275

Re: 2 services (frontend+backend), both with cookies, failure

Hi, On Sat, Oct 11, Kari Mattsson wrote: this got repeated for 50+ times when refreshing on Chrome browser. Then to Firefox.. Oct 11 20:25:17 localhost haproxy[5179]: 10.6.159.238:4248 [11/Oct/2014:20:25:14.300] service_1_outside_80 service_1_inside/App_101 3264/0/0/1/+3265 200 +275 - -

Re: 2 services (frontend+backend), both with cookies, failure

Hi, Hi, and thanks for your reply! On Mon, Oct 06, Kari Mattsson wrote: (IP numbers are imaginary, not real.) When I go to http://200.200.200.111 and http://200.200.200.222, and press F5 (refresh) on Firefox for a few time, I end up with 4 cookies instead of 2. For example when you

Re: 2 services (frontend+backend), both with cookies, failure

Hi, On Mon, Oct 06, Kari Mattsson wrote: (IP numbers are imaginary, not real.) When I go to http://200.200.200.111 and http://200.200.200.222, and press F5 (refresh) on Firefox for a few time, I end up with 4 cookies instead of 2. For example when you go to .111 and hit refresh few times do

Re[2]:

Hi all, Actually I asked this question because I saw a lot of times systems that had more than 10Gb of free physical memory and they anyway used swap partition(about 1-5 Mb). I saw that happened on FreeBSD and on Linux, so I thought it's possible to see that again when I'll run HAProxy. And I

Re: Re[2]:

On 19 March 2011 10:58, Antony ddj...@mail.ru wrote: Hi all, Actually I asked this question because I saw a lot of times systems that had more than 10Gb of free physical memory and they anyway used swap partition(about 1-5 Mb). I saw that happened on FreeBSD and on Linux, so I thought

Re[2]: HEADSUP: Freebsd port net/haproxy-devel to update from v1.3.25 to v1.5-dev1

(Ugh, sorry Willy for the direct email.) And to close out the thread: The new version is now live with version v1.5-dev2 (port version : v1.5.d2) in the ports tree. Do a portsnap update to see it and install it. WT That's not expected since the version is hard-coded in the VERSION file. WT

Re[2]: HEADSUP: Freebsd port net/haproxy-devel to update from v1.3.25 to v1.5-dev1

With the recent announcement of haproxy v1.5-dev1 with it's new features that I'm sure people will want to test, I'll be bringing the port net/haproxy-devel in line with it's name, ie: development. WT That's great news ! However please upgrade to 1.5-dev2 to limit bug WT reports. The freebsd

Re[2]: [ANNOUNCE] haproxy-1.4.2

HJ By compiling Haproxy 1.4.2 on Opensolaris b134 I noticed a warning in HJ dumpstats.c. I don't know for sure if this is a problem, but I thought I HJ let you know. Got the same on Freebsd - but a touch more descriptive message. -= start gcc -Iinclude -Iebtree -Wall -O2 -g -DTPROXY

Re[2]: [ANNOUNCE] haproxy-1.4.0

WT Using the following patch I can build it everywhere here without a WT warning. Could you please test on your various FreeBSD versions, I WT see no reason why it should change anything, it's just for the sake WT of completeness. Compiles without error on FB 7+8! Cheers, Ross. --

Re[2]: [ANNOUNCE] haproxy-1.4.0

Good morning everyone, WT I hope you don't mind that I CC the list and Krzysztof who needed WT the line which caused the problem on your side. No problem, I just hit reply, rather than reply-all out of habit. However, instead of using _XOPEN_SOURCE we may use something less invasive (I hope),

Re: Re[2]: FreeBSD Ports: bumping haproxy from v1.2.18 - v1.4.x

Also, changing -devel right now at the same will cause all sorts of support issues as people deal with the migration - not everyone reads the UPDATING file before issuing portupgrade -a. Even a solution should be to mark the haproxy-devel has Moved (see /usr/ports/MOVED) I see in

Re[2]: [ANNOUNCE] haproxy 1.4-dev5 with keep-alive :-)

That's more of an issue with the site than a (proxy based) load balancer - the LB would be doing the exact same thing as the client. WT Precisely not and that's the problem. The proxy cannot ask the user WT if he wants to retry on sensible requests, and the cannot precisely WT know what is at

Re[2]: [ANNOUNCE] haproxy 1.4-dev5 with keep-alive :-)

I'll enter in this conversation as I've used (successfully) a load balancer which did server-side keep-alive a while ago. WT Hmmm that's different. There are issues with the HTTP protocol WT itself making this extremely difficult. When you're keeping a WT connection alive in order to send a

Re[2]: [ANNOUNCE] haproxy 1.4-dev5 with keep-alive :-)

WT It's not only a matter of caching the request to replay it, it is that WT you're simply not allowed to. I know a guy who ordered a book at a WT large well-known site. His order was processed twice. Maybe there is WT something on this site which grants itself the right to replay a user's WT

Re[2]: Geographic loadbalancing

JL I would like to hear anyone using anycast with TCP. What if two servers are JL equal distance. Wouldn't you have a fair chance of equal 50% packets going JL each way, killing tcp state connections. The more servers out there JL advertising the same IP, the more likely you will have cases of