[Issue] Update Curl to respect case-insensitive headers

[m2-assistant]

This issue is automatically created based on existing pull request: #29274: Update Curl to respect case-insensitive headers

---

According to RFC 2616 header names are case-insensitive: "Each header field consists of a name followed by a colon (":") and the field value. Field names are case-insensitive." - see https://tools.ietf.org/html/rfc2616#section-4.2

The "Set-Cookie" comparison in the current Curl client is case-sensitive and can cause problems with some (rare) HTTP servers.

Preconditions: (*)

Magento 2.4-develop

According to RFC 2616 header names are case-insensitive: "Each header field consists of a name followed by a colon (":") and the field value. Field names are case-insensitive." - see https://tools.ietf.org/html/rfc2616#section-4.2

The "Set-Cookie" comparison in the previous version is case-sensitive and can cause problems with some (rare) HTTP servers.

Related Pull Requests

None

Fixed Issues (if relevant)

Did not create an issue

Steps to reproduce:

1. Need to become a debugger to check the value on line:

 if ("Set-Cookie" == $name) {

2. Go to Admin -> Find Partners & Extensions (for example);

Actual Result: ✖️ It doesn't respect those header names ("set-cookie" or "SET-COOKIE")

Expected Result: ✔️ It should respect those header names

Questions or comments

Please note that I did not provide a unit test for this specific issue. If required please let me know.

Contribution checklist (*)

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• All automated tests passed successfully (all builds are green)

[magento-engcom-team]

✅ Confirmed by @engcom-Alfa
Thank you for verifying the issue. Based on the provided information internal tickets MC-37706 were created

Issue Available: @engcom-Alfa, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[magento-engcom-team]

Hi @m2-assistant[bot]. Thank you for your report.
The issue has been fixed in #29274 by @pmzandbergen in 2.4-develop branch
Related commit(s):

• 44d88e64f70134280616bcc9471f74283fdef44f
• ba6513fa9b8777dd5a1a89a9b542ec54978ef534
• 730c49543f9d4f74fde690b42279ddfd140577e9
• 552e0c1fbd1367e7ecb7fb421b8057060663a3af
• b5463b82e919dca2afff595a1d55c116a1ab50bc
• e43e45fac11c585855d2da5a5bb6c2a58d28fb68
• e1d21cd8b3a9ac3c400ba01b88bcd1ed80f6e3a8
• 9570f8f0efe9cb77fe7a430843167ad5f879682a
• 9db1f830052f990103845b1ecac03b45091c51cb
• d61e030601cc220944d81c7d793b458356ba93d3
• e912bdf9fe115d7f9cf48d41502d0d6d16713c08
• d5c674d8f640ffb655b80aa2959a0a980bcd70bf

The fix will be available with the upcoming 2.4.2 release.