You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 22, 2024. It is now read-only.
We should not cache any error pages ( 404, 500... )
Actual Behavior
Actually even if the rendering contains an error, the page are put in cache.
constcontent=awaitrender();consttags=getTags();if(!tags.length){returncontent;}------>Weshouldcheckifthereisanerrorin`content`<-----// We could add "await" here, but saving content in cache doesn't have to block the requestclient.set(key,content,tags);
Possible Solution
Add a check for content.error variable and do not cache the response.
Steps to reproduce
Hit a 404 page.
What version of Magento 2 integration are you using?
2.4.3
What version of Node.js are you using?
16
What browser (and version) are you using?
Chrome
What operating system (and version) are you using?
macOS
Relevant log output
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Expected Behavior
We should not cache any error pages ( 404, 500... )
Actual Behavior
Actually even if the rendering contains an error, the page are put in cache.
Possible Solution
Add a check for
content.error
variable and do not cache the response.Steps to reproduce
Hit a 404 page.
What version of Magento 2 integration are you using?
2.4.3
What version of Node.js are you using?
16
What browser (and version) are you using?
Chrome
What operating system (and version) are you using?
macOS
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: