I'm wondering if there are any significant performance implications for the
order of our ACLs known without doing multiple rounds of testing. Here is
an example mixing path_beg and path_reg.
acl url_wcfg path_beg -i /portal /portal/ /reports /reports/
use_backend Portal if url_wcfg
acl url_presentation path_reg -i ^/presentation/.*
^/[a-zA-Z0-9_]*/presentation/.* ^/[a-zA-Z0-9_]*/session/.*
^/[a-zA-Z0-9_]*/session ^/realtime ^/realtime/.*
use_backend Presentation if url_presentation
acl url_custom path_reg -i /[a-zA-Z0-9_]*/ext/.*
use_backend Custom if url_custom
acl url_api path_beg -i /api/
use_backend Api if url_api
acl url_MobileApps path_beg -i /apps/
use_backend MobileApps if url_MobileApps
acl url_staticresources path_beg -i /content/ /resources/ /system/
use_backend StaticResources if url_staticresources
acl url_persistent path_beg -i /charts/ /scoring/ /upload/
use_backend PersistentApps if url_persistent
default_backend Shared
Assuming relative equal hits to the ACLs, is the performance of path_beg
relatively inline with path_reg or would we get better performance by
putting the path_beg entries first?
Thank you,
Sean
--
--- "The obscure we see eventually, the completely apparent takes longer"
---- Edward R. Murrow
