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
Correct the way that haproxy uses the secure cookie attribute #12802
Conversation
the only time that we dont want a cookie flagged as secure is when the InsecureEdgePolicy is set to Allow, currently that is not the case This patch changes the conditional and flags cookies as secure appropriately
@openshift/networking |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
[test] |
Evaluated for origin test up to ddb865e |
continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/13575/) (Base Commit: 5565661) |
Looks good! LGTM |
@ramr PTAL |
[merge] |
Evaluated for origin merge up to ddb865e |
continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/13625/) (Base Commit: e92d661) (Image: devenv-rhel7_5861) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
the only time that we dont want a cookie flagged as secure is when the
InsecureEdgePolicy is set to Allow, currently that is not the case
This patch changes the conditional and flags cookies as secure appropriately
Bug 1412591 Link