Update HTTP status code in RequestTest.php

[guibranco]

Description

• Updated the expected status code in the testCanHead method to reflect the correct behavior.
• This change ensures that the test accurately checks for a 502 status code instead of 200.

---

Changes walkthrough 📝

	Relevant files
Tests	RequestTest.php Update HTTP status code assertion in RequestTest                  tests/RequestTest.php Updated the expected status code in the testCanHead method. Changed the assertion from 200 to 502. +1/-1

[deepsource-io[bot]]

Here's the code health analysis summary for commits 9478681..0c99aae. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
Test coverage	⚠️ Artifact not reported	Timed out: Artifact was never reported	View Check ↗
SQL	✅ Success		View Check ↗
Secrets	✅ Success		View Check ↗
PHP	✅ Success		View Check ↗
Docker	✅ Success		View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[penify-dev[bot]]

PR Review 🔍

⏱️ Estimated effort to review [1-5]	1, because the change is straightforward and involves a simple assertion update in a test method.
🧪 Relevant tests	Yes
⚡ Possible issues	No
🔒 Security concerns	No

[penify-dev[bot]]

PR Code Suggestions ✨

Category	Suggestion	Score
Possible issue	Update the HTTP status code to reflect a successful HEAD request ___ **Consider using a more appropriate HTTP status code for the HEAD request, as 502 indicates a bad gateway error, which may not be the expected outcome for a successful HEAD request.** [tests/RequestTest.php [65]](https://github.com/guibranco/pancake/pull/218/files#diff-36a89d6e0cddbb18aca0954479d96fa1fae84c7a87bf8dcf75b89e1eebe71319R65-R65) ```diff -$this->assertEquals(502, $response->statusCode); +$this->assertEquals(200, $response->statusCode); ``` Suggestion importance[1-10]: 9 Why: The suggestion correctly identifies that a 502 status code is inappropriate for a successful HEAD request, which should return a 200 status code. This change addresses a significant issue in the test logic.	9

[github-actions[bot]]

Infisical secrets check: :white_check_mark: No secrets leaked!

Scan results:

2:22PM INF scanning for exposed secrets...
2:22PM INF 149 commits scanned.
2:22PM INF scan completed in 408ms
2:22PM INF no leaks found