Project

General

Profile

Actions

Feature #3583

closed

haproxy-devel: individual backend for each acl

Added by Andreas Morf almost 10 years ago. Updated about 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
haproxy
Target version:
-
Start date:
04/08/2014
Due date:
% Done:

0%

Estimated time:
Plus Target Version:

Description

To define several backends based on acl's for one frontend a backend selection iten is recommended for each acl - current selection of backend within basic frontend parameters is not providing enough flexibility.

Actions #1

Updated by Pi Ba about 9 years ago

Using the 'shared frontends' its possible to define acl's for different backends, this should allow for 'most' common scenarios to be defined in the webgui.

Can you elaborate what you have in mind exactly? Perhaps you could give an example of the haproxy.cfg acl's as you would like to be able to create using the webgui?

Actions #2

Updated by Chris Buechler about 8 years ago

  • Project changed from pfSense to pfSense Packages
  • Category set to haproxy
  • Status changed from New to Closed
  • Priority changed from High to Normal
  • Target version deleted (Future)

seems this exists already, as PiBa noted.

Actions

Also available in: Atom PDF