Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't use backend name to generate acl name #726

Merged
merged 2 commits into from Nov 28, 2017

Conversation

Projects
None yet
1 participant
@tamalsaha
Copy link
Member

commented Nov 28, 2017

ref:
https://www.haproxy.com/documentation/aloha/7-0/haproxy/acls/

Backend names are empty for paths that are auto injected for redirect rules. So, we can't assume that backend names will always be present.

@tamalsaha tamalsaha requested a review from diptadas Nov 28, 2017

@tamalsaha tamalsaha force-pushed the fix-tpl branch from 974f4d6 to 50c3eec Nov 28, 2017

@tamalsaha tamalsaha force-pushed the fix-tpl branch from 50c3eec to 169023d Nov 28, 2017

@tamalsaha tamalsaha added the bug label Nov 28, 2017

@tamalsaha tamalsaha merged commit bb5cd74 into master Nov 28, 2017

@tamalsaha tamalsaha deleted the fix-tpl branch Nov 28, 2017

tamalsaha added a commit that referenced this pull request Dec 12, 2017

Don't use backend name to generate acl name (#726)
ref:
https://www.haproxy.com/documentation/aloha/7-0/haproxy/acls/

Backend names are empty for paths that are auto injected for redirect rules. So, we can't assume that backend names will always be present.

tamalsaha added a commit that referenced this pull request Dec 13, 2017

Don't use backend name to generate acl name (#726)
ref:
https://www.haproxy.com/documentation/aloha/7-0/haproxy/acls/

Backend names are empty for paths that are auto injected for redirect rules. So, we can't assume that backend names will always be present.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.