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
Bug 1852728: haproxy 503 error page: replace all LF by CRLF to be fully RFC compliant #140
Bug 1852728: haproxy 503 error page: replace all LF by CRLF to be fully RFC compliant #140
Conversation
…with rfc2616 and rfc 7230
Hi @felixkrohn. Thanks for your PR. I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
P.S. Checking the 503 error file of upstream HAproxy, I noticed they have the RFC-compliant CRLF, so it should be no big issue for Openshift-HAproxy either:
(0d0a is CRLF) |
@JacobTanenbaum @pecameron Do you have any objections or see other blockers to get this one merged? |
/ok-to-test |
/retest |
5 similar comments
/retest |
/retest |
/retest |
/retest |
/retest |
This is LGTM for me. Adding @openshift/openshift-team-network-edge in case we deliberately had this as LF only for specific reasons. |
/lgtm |
@felixkrohn a BZ will need to be created and linked if you need this fix in 4.6. |
@danehans Thanks! BZ #1852728 already exists, can you somehow link it? |
/retitle Bug 1852728: haproxy 503 error page: replace all LF by CRLF to be fully RFC compliant |
@felixkrohn: This pull request references Bugzilla bug 1852728, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
hm, @danehans isn't in the approvers list @felixkrohn we will backport this PR for 4.5, 4.4, and 3.11 later this week most likely. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: danehans, felixkrohn, sgreene570 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@sgreene570 Wonderful! Thanks, this is very much apreciated. |
@felixkrohn: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
/retest Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
/retest Please review the full test history for this PR and help us cut down flakes. |
@felixkrohn: All pull requests linked via external trackers have merged: Bugzilla bug 1852728 has been moved to the MODIFIED state. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/cherry-pick release.4-5 |
/cherry-pick release.4-4 |
@sgreene570: cannot checkout release.4-5: error checking out release.4-5: exit status 1. output: error: pathspec 'release.4-5' did not match any file(s) known to git In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@sgreene570: cannot checkout release.4-4: error checking out release.4-4: exit status 1. output: error: pathspec 'release.4-4' did not match any file(s) known to git In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
whoops, try that again. |
@sgreene570: new pull request created: #181 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/cherry-pick release-4.4 |
@sgreene570: new pull request created: #182 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
rfc2616 and rfc7230 both demand that in HTTP messages lines be ended with CRLF.
Although both RFCs stipulate that LF-only line endings MAY or even SHOULD be accepted, It's better to be fully compliant. Very picky HTTP clients, such as web access firewalls, may trip over this and blame Openshift's router.
This PR is whitespace-only and converts all LF line terminators in this file to CRLF.