Re: req.body_param([])

Dear Jarno, Thanks for the feedback on this. I investigated further to find the solution to this issue. It turned out that not all PUT requests had a problem with filtering out the customerId parameter we're looking for. Some requests seem to encode the HTTP PUT body somehow or have set some

BUG: ssl: regression with openssl 1.1.1 when using <= TLSv1.2

Hey guys, we have a regression in 1.8 and -dev with OpenSSL 1.1.1 (from the first beta to current master): when strict-sni is set, TLSv1.0 and TLSv1.1 does not work (TLSv1.2 is fine). I haven't tested whether SNI based certificate selection is broken as well, but strict-sni definitely rejects TLS

Re: SPOE and modsecurity contrib

> Em 20 de mai de 2018, à(s) 11:59, Daniel Corbett > escreveu: > > Hello Joao, > > While I haven't been able to get 'tcp-request content reject' to work with > this configuration -- I am able to get 'http-request deny' to work: > > http-request deny if { var(txn.modsec.code) -m int gt 0 } >

[PATCH] MINOR: http: Log warning if (add|set)-header fails

Willy, attached is a first attempt at a patch that adds logging (without any rate limiting). I have a few questions regarding the whole counters and logging infrastructure: 1. I noticed that there is ha_warning(...) and send_log(p, LOG_WARNING, ...), usually both are used in the same place. Wh

Re: SPOE and modsecurity contrib

Hello Joao, While I haven't been able to get 'tcp-request content reject' to work with this configuration -- I am able to get 'http-request deny' to work: http-request deny if { var(txn.modsec.code) -m int gt 0 } Regarding txn.modsec.code -- I have been able to reproduce the "txn.modsec.co