Iām adding UpcomingSprint, because I was occupied by fixing bugs with higher priority/severity, developing new features with higher priority, or developing new features to improve stability at a macro level. I will revisit this bug next sprint.
The merge made into "v3.11.273-1_2020-08-30.1" release version with the included "haproxy18-1.8.23-3" package version. It is noted that the headers now contain CR-LF linebreaks: ----- $ hexdump -C share/haproxy/503.http | head -n3 00000000 48 54 54 50 2f 31 2e 30 20 35 30 33 20 53 65 72 |HTTP/1.0 503 Ser| 00000010 76 69 63 65 20 55 6e 61 76 61 69 6c 61 62 6c 65 |vice Unavailable| 00000020 0d 0a 43 61 63 68 65 2d 43 6f 6e 74 72 6f 6c 3a |..Cache-Control:| -----
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 3.11.317 bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:4430