Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Magento\Framework\Filesystem\Driver\Http depends on reason phrase OK #39546

Open
1 of 5 tasks
jirichmiel opened this issue Jan 15, 2025 · 10 comments
Open
1 of 5 tasks

Magento\Framework\Filesystem\Driver\Http depends on reason phrase OK #39546

jirichmiel opened this issue Jan 15, 2025 · 10 comments
Labels
Area: Framework Component: HTTP Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Reported on 2.4.x Indicates original Magento version for the Issue report. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Triage: Dev.Experience Issue related to Developer Experience and needs help with Triage to Confirm or Reject it

Comments

@jirichmiel
Copy link

Summary

Method Magento\Framework\Filesystem\Driver\Http::isExists that determines whether given url exists depends on that remote server returns status header with 200 OK (e.g: HTTP/1.1 200 OK), but reason phrase OK is not required (https://www.rfc-editor.org/rfc/rfc7230#section-3.1.2). Some server may return only HTTP/1.1 200. In that case Driver\Http will tell that given url does not exist although it exists.

Examples

~$ curl -i "https://acs4.editionguard.com/fulfillment/URLLink.acsm"
HTTP/1.1 200 
Content-Type: application/vnd.adobe.adept+xml
Date: Wed, 15 Jan 2025 18:49:25 GMT
Server: Apache/2.4.39 (Amazon) OpenSSL/1.0.2k-fips
Content-Length: 139
Connection: keep-alive

Proposed solution

Change line from

return !(strpos($status, '200 OK') === false);

to

return !(strpos($status, '200') === false);

Release note

No response

Triage and priority

  • Severity: S0 - Affects critical data or functionality and leaves users without workaround.
  • Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
  • Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
  • Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
  • Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.
@jirichmiel jirichmiel added the Triage: Dev.Experience Issue related to Developer Experience and needs help with Triage to Confirm or Reject it label Jan 15, 2025
Copy link

m2-assistant bot commented Jan 15, 2025

Hi @jirichmiel. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.


Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

@engcom-Bravo engcom-Bravo added the Reported on 2.4.x Indicates original Magento version for the Issue report. label Jan 16, 2025
@github-project-automation github-project-automation bot moved this to Ready for Confirmation in Issue Confirmation and Triage Board Jan 16, 2025
@engcom-Hotel engcom-Hotel self-assigned this Jan 16, 2025
Copy link

m2-assistant bot commented Jan 16, 2025

Hi @engcom-Hotel. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

  • 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
  • 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
  • 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
  • 4. Verify that the issue is reproducible on 2.4-develop branch
    Details- If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
    - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
  • 5. Add label Issue: Confirmed once verification is complete.
  • 6. Make sure that automatic system confirms that report has been added to the backlog.

@engcom-Hotel
Copy link
Contributor

Hello @jirichmiel,

Thanks for the report and collaboration!

We have reviewed the codebase here:

public function isExists($path)
{
$headers = array_change_key_case(get_headers($this->getScheme() . $path, 1), CASE_LOWER);
$status = $headers[0] ?? '';
/* Handling 301 or 302 redirection */
if (isset($headers[1]) && preg_match('/30[12]/', $status)) {
$status = $headers[1];
}

And also went through the link here and found that it does not necessarily return 200 OK, hence confirming this issue. I also suggest you to raise a community PR with this fix.

Thanks

@engcom-Hotel engcom-Hotel added Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Component: HTTP Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Area: Framework labels Jan 16, 2025
@github-jira-sync-bot
Copy link

✅ Jira issue https://jira.corp.adobe.com/browse/AC-13725 is successfully created for this GitHub issue.

Copy link

m2-assistant bot commented Jan 16, 2025

✅ Confirmed by @engcom-Hotel. Thank you for verifying the issue.
Issue Available: @engcom-Hotel, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

@ajith107
Copy link

@magento I am working on this

Copy link

m2-assistant bot commented Jan 20, 2025

Hi @ajith107! 👋
Thank you for collaboration. Only members of Community Contributors Team are allowed to be assigned to the issue. Please use @magento add to contributors team command to join Contributors team.

@ajith107
Copy link

@magento add to contributors team

Copy link

m2-assistant bot commented Jan 20, 2025

Hi @ajith107! 👋
Thank you for joining. Please accept team invitation 👉 here 👈 and add your comment one more time.

@ajith107
Copy link

@magento I am working on this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Framework Component: HTTP Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Reported on 2.4.x Indicates original Magento version for the Issue report. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Triage: Dev.Experience Issue related to Developer Experience and needs help with Triage to Confirm or Reject it
Projects
Status: Pull Request In Progress
Development

No branches or pull requests

5 participants