ha-proxy: action order in the GUI is not keeped in the resulting ha-proxy configuration
If there are (for example) 'Use Backend' and 'http-request redirect' actions are defined in the GUI in a specific order - let's say
(1) use backend | acl_1 | backend_1
(2) http-request Redirect | acl_3 | rule: code 301 location https://%[hdr(host)]%[path]
(3) http-request Redirect | acl_4 | rule: code 301 location https://%[hdr(host)]%[path]
(4) use backend | acl_2 | backend_2
(5) http-request Redirect | acl_5 | rule: code 301 location https://%[hdr(host)]%[path]
(6) use backend | acl_6 | backend_6
the resulting ha-proxy configuration contains all 'http-request redirect' actions (in the right order) followed by all 'Use Backend' actions (in the right order)
instead keeping the complete defined action order (1....6).
I know the GUI-code is completely designed to work this way (collect and group different actions in separate arrays and processing these arrays one after the other) - so, this is not a bug.
Knowing how it is working, acl's and actions can be defined to get them working like needed.
But it can be expected, that the action order is keeped like defined, because we can define and change their order in the GUI.
I see the following options to solve the problem:
- change the code to keep the defined action order in the resulting ha-proxy configuration (the very best option, but the one with the largest effort)
- write a hint to the GUI, which clearly states the processing order of all possible actions
- provide a "check result" (or similar) button in the GUI, which shows the resulting action order
Without knowing how this feature works in pfsense, it is nearly impossible to define a more complex (but working) ha-proxy configuration.
No data to display