-
Notifications
You must be signed in to change notification settings - Fork 192
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
DO NOT MERGE: Use Hit-For-Pass if Cache-Control response headers contain "no-cache" or "no-store" #322
base: develop
Are you sure you want to change the base?
Conversation
- Use Hit-For-Pass if Cache-Control response headers contain "no-cache" or "no-store"
Unit & Integration Test Results✅ All unit and integration tests have passed. Unit Test Output
Integration Test Output
This comment was generated by Jenkins job magento-cloud-docker/unit build 23. |
Static Analysis & Code Style Results✅ All static analysis and code style checks have passed. PHP Codesniffer Output
PHP Mess Detector Output
PHPStan Output
This comment was generated by Jenkins job magento-cloud-docker/static build 24. |
|
Functional Acceptance Test Results❌ One or more functional acceptance tests have failed. PHP 7.2
PHP 7.3
PHP 7.4
Output for failed tests is below. If many tests have failed only the first 5 will be included. If you need additional information please reach out to the Magento Cloud team for more details. This comment was generated by Jenkins job magento-cloud-docker/functional build 28. |
PHP 7.4 SplitDbCest Output
This comment was generated by Jenkins job magento-cloud-docker/functional build 28. |
@shiftedreality , @oshmyheliuk do you know the latest status on this PR? Did we have a chance to review? |
Description
Current default.vcl file is caching responses even if they contain "no-cache" or "no-store" in Cache-Control response headers. To verify this misbehavior, run \Magento\Webapi\WsdlGenerationFromDataObjectTest in SOAP mode. Notice that:
/soap/default?wsdl=1&services=testModule5AllSoapAndRestV2
with GET method; Authorization header is required to get a successful response. The Authorization header is passed in the request and generates 200 response.Compare this proposed change to repos that already use it:
https://github.com/magento/magento2/blob/2.4-develop/app/code/Magento/PageCache/etc/varnish6.vcl#L184
https://github.com/magento-cicd/cicd-docker/blob/master/dfiles/mdc-jenkins/scripts/varnish.vcl#L191
Fixed Issues (if relevant)
Manual testing scenarios
Release notes
For user-facing changes, add a meaningful release note. For examples, see Magento Cloud Docker release notes.
Associated documentation updates
Add link to Magento DevDocs PR or Issue, if needed.
Contribution checklist