Re: [PR] Fix backend typo

Hi Rick, thanks for your first patch. I've adjusted the commit message and merged it. Please next time have a look at CONTRIBUTING to see how to properly format your commit messages and submit your patches, this makes the process smoother and does help quite a bit. Thanks, Willy

Re: Query: Respond with same tos/dscp value as incoming request tos/dscp value

Hi Nikhil, On Tue, Oct 08, 2019 at 04:09:49PM +0530, Nikhil Agrawal wrote: > Hi, > > I have a use case where i need http response from haproxy with same > tos/dscp value as incoming packet. > > I found the set-tos in haproxy but no option to dynamically set the same as > incoming request. > >

Re: Issue with HTX

Hi Ionel, On Tue, Oct 08, 2019 at 03:33:16PM +0200, GARDAIS Ionel wrote: > Hi, > > I'm facing a data corruption that seems related to HTX. > Simply adding 'no option http-use-htx' solve the issue. > > What kind of traces do you need to help diagnose the issue and how to collect > it ?

Issue with HTX

Hi, I'm facing a data corruption that seems related to HTX. Simply adding 'no option http-use-htx' solve the issue. What kind of traces do you need to help diagnose the issue and how to collect it ? Thanks, Ionel -- 232 avenue Napoleon BONAPARTE 92500 RUEIL MALMAISON Capital EUR 219

Query: Respond with same tos/dscp value as incoming request tos/dscp value

Hi, I have a use case where i need http response from haproxy with same tos/dscp value as incoming packet. I found the set-tos in haproxy but no option to dynamically set the same as incoming request. Is there any way to do the same in haproxy. Thanks in advance. Regards, Nikhil Agrawal --

[PR] Fix backend typo

Dear list! Author: Rick Rackow Number of patches: 1 This is an automated relay of the Github pull request: Fix backend typo Patch title(s): Fix backend typ Link: https://github.com/haproxy/haproxy/pull/316 Edit locally: wget https://github.com/haproxy/haproxy/pull/316.patch &&

"official" rpm repo ?

hi, I played a bit with Fedora COPR (it is nice) https://copr.fedorainfracloud.org/coprs/chipitsine/haproxy/build/1041926/ few questions 1) do we insist on Lua support ? (it is hard to get Lua-5.3 for EPEL7) 2) any best practice on building new packages ? anyway, I do not insist in running

Re: healthchecks (to uwsgi) possible regression 1.9.8 -> 1.9.9

Hi Jarno, On Fri, Oct 04, 2019 at 07:28:15PM +0300, Jarno Huuskonen wrote: > I sent pcap/strace offlist. Thanks, that was very useful. > (strace -f -o -ttt, tcpdump -n -p -s 16384 -w ... host 127.0.0.1 and > port 8080). > > I think in packet capture the second health checks causes >