http: fix Curl_compareheader for multi value headers

[bagder]

Follow-up to 04289c6. Regression shipped in 8.13.0.

• a logic error made it not loop and thus only match if the searched string was first

• it no longer matches a substring

Adjusted test 1 to use multiple values in the Connection: response header.

Reported-by: Henrique Pereira

[bagder]

augment review

[augmentcode]

🤖 Augment PR Summary

Summary: Fixes Curl_compareheader() to correctly scan comma-separated, multi-value HTTP headers and only match whole tokens.
Why: Addresses a regression shipped in 8.13.0 where only the first value was checked and substring matching behavior changed; updates test1 to cover multi-value Connection: responses.

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. No suggestions at this time.

Comment augment review to trigger a new review at any time.

[Copilot]

Pull request overview

Fixes a regression in Curl_compareheader() (introduced after 04289c6) so that multi-value HTTP headers are properly searched again, and updates the relevant test data to include a multi-value Connection: response header.

Changes:

• Update Curl_compareheader() logic intended to iterate over comma-separated header values again.
• Adjust tests/data/test1 to use multiple values in the Connection: response header.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
tests/data/test1	Updates the canned HTTP response to include multi-value Connection: header values.
lib/http.c	Changes the header value matching loop in Curl_compareheader() to handle multiple values.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review. Take the survey.