All,
I got it working more or less I can bypass HTTP basic auth in case there is an
existing session of the user via the primary backend application.
What’s missing is the cleanup part of dynamic ACLs after session timeout where
I need some help.
This is the working configuration:
On 29.10.2014, at 16:42, Baptiste bed...@gmail.com wrote:
This is doable with HAProxy 1.6-dev.
You have to store the answered cookie in a table when generated by the
server and then match it into the same table when the client sends it.
Thanks for the hint! Maybe I find another workaround
Hi folks,
I was wondering if there is a way to have HAproxy check for an existing Cookie
the client sends and have it verify with a specific backend (say backend1).
Based on that backends HTTP error code (e.g. 200 or 403), HAproxy should allow
forwarding to backend2. Of course this would need
On 28.10.2014, at 10:13, Julian Pawlowski jul...@pawlowski.me wrote:
I was wondering if there is a way to have HAproxy check for an existing
Cookie the client sends and have it verify with a specific backend (say
backend1). Based on that backends HTTP error code (e.g. 200 or 403), HAproxy
4 matches
Mail list logo
