Re: any way to get longer header names in haproxy?

Hello, On Wed, Oct 18, 2023 at 11:31:30AM -0700, Jerry Scharf (he/him/his) wrote: > We use haproxy for https termination for one of our services. We are trying > to upgrade to late model haproxy, but have run into a problem. In old > haproxy versions, it allowed 1k header names and we told our

Formilux - Global Sources Consumer Electronis Show 2023

Hi there, I hope this message finds you well. Are you interested in procuring an event visitor database? The event details are as follows: Global Sources Consumer Electronis Show 2023 :60137 Contacts If this opportunity interests you, I'm ready to furnish you with the comprehensive information.

any way to get longer header names in haproxy?

We use haproxy for https termination for one of our services. We are trying to upgrade to late model haproxy, but have run into a problem. In old haproxy versions, it allowed 1k header names and we told our customers that. In modern versions, it is checked and limited to 254. I saw that this check

Re: [PATCH] MINOR: lua: Add a flag to disable logging to stderr

By the way, since we're talking about it, I think that actually it's not logs that we're sending to stderr, it's Lua's alert messages that we're sending both to stderr and logs. Well I am no expert in what qualifies as "logs" vs "alerts", but the messages sent from (for example) txn:Info()

Re: [PATCH] MINOR: lua: Add a flag to disable logging to stderr

On Wed, Oct 18, 2023 at 04:23:06PM +, Tristan wrote: > Hi Willy, > > > On 18/10/2023 07:47, Willy Tarreau wrote: > > Hi Tristan, > > > > ... > > > > I'm fine with the general approach, but I'm having two comments: > > > >- using the word "also" in the option name is really not welcome

Re: [PATCH] MINOR: lua: Add a flag to disable logging to stderr

... One last thing, SEND_ERR() reports to stderr through ha_alert() and hlua_sendlog() does it through fprintf(stderr, ) by appending a static header containing the log level, the date and the pid: maybe we should try to unify those outputs as well? I'm not sure anyone really *wants* to

Re: [PATCH] MINOR: lua: Add a flag to disable logging to stderr

Hi Willy, On 18/10/2023 07:47, Willy Tarreau wrote: Hi Tristan, ... I'm fine with the general approach, but I'm having two comments: - using the word "also" in the option name is really not welcome ("tune.lua.also-log-to-stderr"), and actually more confusing than without

Re: [PATCH] MINOR: lua: Add a flag to disable logging to stderr

Hi Aurélien, On Wed, Oct 18, 2023 at 09:32:19AM +0200, Aurelien DARRAGON wrote: > Hi Guys, > > I also have a suggestion, while at it: > > SEND_ERR() which is used to report unexpected Lua errors (because of > improper API usage, or due to external factors such as IO/memory issues) > currently

Re: [PATCH 2/4] MEDIUM: connection: Send out generically allocated proxy-v2-options

Hi Alexander, I'm starting from the doc as it eases the discussion. On Thu, Oct 05, 2023 at 11:05:50AM +, Stephan, Alexander wrote: > --- a/doc/configuration.txt > +++ b/doc/configuration.txt > @@ -16671,6 +16671,26 @@ proxy-v2-options [,]* > generated unique ID is also used

Re: [PATCH] MINOR: lua: Add a flag to disable logging to stderr

Hi Guys, I also have a suggestion, while at it: SEND_ERR() which is used to report unexpected Lua errors (because of improper API usage, or due to external factors such as IO/memory issues) currently does a stderr duplication as in hlua_sendlog() I'm thinking that it could be useful to make

Re: [PATCH] MINOR: lua: Add a flag to disable logging to stderr

Hi Tristan, On Tue, Oct 17, 2023 at 06:19:57PM +, Tristan wrote: > By default, messages printed from LUA log functions are sent both to > the configured log target and additionally to stderr (in most cases). > This introduces tune.lua.also-log-to-stderr for disabling that > second copy of the