Skip to content

Conversation

@pierrecdn
Copy link

As of HAProxy 3.0+, these options are:

  • either marked deprecated (req_ssl_sni, req_ssl_hello_type) in the config.
  • either it is advised to do differently (no-sslv3, no-tlsv10)

ServerSwitchingRule Server Switching Rule
HAProxy server switching rule configuration (corresponds to use-server directive)
Example: {"cond":"if","cond_test":"{ req_ssl_sni -i www.example.com }","target_server":"www"}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This file is actually generated from a client-native model and can not be changed here.
I can open a MR in client-native to change this.
We also need to add a CI check to check that this file is not updated manually.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, indeed.
So should I remove that one only and let you perform the merge for the rest (and then the bump of client-native)?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did this, also tried to match the check-commit.

@pierrecdn pierrecdn changed the title MINOR: remove deprecated config options CLEANUP/MINOR: remove deprecated config options Feb 11, 2026
@hdurand0710
Copy link
Member

hdurand0710 commented Feb 11, 2026

@pierrecdn , There is also a CI complain on the commit message:

2026/02/10 16:19:05 aspell.go:189: commit message aspell: [req sslv tlsv]
These come from the names with underscores in the commit message.
The simplest way is to add those 3 req, sslv and tlsv in the file /.aspell.yml at the root.
Thanks!

These options are either marked deprecated (req_ssl_sni, req_ssl_hello_type)
in the config. or it is advised to do differently (no-sslv3, no-tlsv10) as
of HAProxy 3.0+.
@hdurand0710
Copy link
Member

@pierrecdn ,
Now we have a Bad Credential issue with the check-commit...
We will fix that internally.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants