Laminas/HTTP/Response add extra space in header value

[HeenaBansal20]

Bug Report

Q	A
Version(s)	All

Summary

HTTP/Response::getHeaders() returns header like key:<space>value even when the header sent by application is key:value .

HTTP spec says :
https://www.rfc-editor.org/rfc/rfc9110.html#name-whitespace

The OWS rule is used where zero or more linear whitespace octets might appear. For protocol elements where optional whitespace is preferred to improve readability, a sender SHOULD generate the optional whitespace as a single SP; otherwise, a sender SHOULD NOT generate optional whitespace except as needed to overwrite invalid or unwanted protocol elements during in-place message filtering

.

Current behavior

sendResponse(method, requestTarget, resOrStream, 200, JSON.stringify(incomingHeaders2, null, 2), {
    'Content-Type': 'application/json',
    'X-Response-Header-Downstream-To-App': 'Value 3',
  });
}

However when reading headers from laminas/API/response::getHeaders() , I received the headers like:

'Content-Type':  'application/json',
'X-Response-Header-To-App':  'Value 3'

How to reproduce

Any node js application which sends header in above format and laminas application received the requests and print headers.

Expected behavior

headers should propagated as it is what framework received.

[froschdesign]

@HeenaBansal20
Thanks for reporting this! 👍🏻
Can you create a unit test that illustrates the problem and then we can see what the continuous integration checks say.

[HeenaBansal20]

For example in the current header test
https://github.com/laminas/laminas-http/blob/2.22.x/test/HeadersTest.php#L106
if you send header as
$headers->addHeaderLine('foo:bar1,bar2,bar3');

getHeaders() shouldn't return 'foo: bar1,bar2,bar3'

[froschdesign]

Please create a unit test and send this as pull request.