Order of acl rules

[sttts]

The web ui allows to define haproxy ACLs, but not the order they are applied, i.e. the order of use_backend lines in the config. I propose to add an order either by drag'n'drop in the UI or by a priority value in order to allow use cases like these:

• route requests with a certain header to canary instances of an app
• route unknown domains to a default app.

[nickandrew]

Agreed. The default setting of "use path to determine backend" may be incorrectly applied before using the host header to find the backend. Being able to reorder the definitions in the UI would sort this out, or using a priority value would be useful with REST.

[j1n6]

Ordering seems to be a good feature to add. I'll take a look storage, REST API and UI for this.

[xiaods]

• route unknown domains to a default app. this feature is well defined.
• route requests with a certain header to canary instances of an app. (Does anyone can tell a case to clarify the context? i am not understand the context.

[bsideup]

:+1:

[dgrizzanti]

Has there been any traction on this? Issue seems old but interested in potentially taking advantage of this.