On 7/5/23 15:27, Pavlos Parissis wrote:
There is a list of pre-defined ACLs, see
http://docs.haproxy.org/2.8/configuration.html#7.4, and in that list
you have HTTP_1.0 acl to match traffic for that version of HTTP protocol.
So, you can add below snippet to block traffic for HTTP 1.0 version
On Wednesday, July 5, 2023 8:25:35 PM CEST Shawn Heisey wrote:
> I have a backend in haproxy for my Solr server. Solr lives unencrypted
> on port 8983, haproxy provides TLS for it, on a name like
> `solr.example.com`.
>
> Everything works fully as expected with HTTP 1.1, 2, or 3.
>
> If I
I have a backend in haproxy for my Solr server. Solr lives unencrypted
on port 8983, haproxy provides TLS for it, on a name like
`solr.example.com`.
Everything works fully as expected with HTTP 1.1, 2, or 3.
If I send a request with curl using any HTTP version to
https://solr.example.com/,
3 matches
Mail list logo