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

Category X-Magento-Tags too long causing Varnish to 503 #8696

Closed
djfordz opened this issue Feb 27, 2017 · 3 comments
Closed

Category X-Magento-Tags too long causing Varnish to 503 #8696

djfordz opened this issue Feb 27, 2017 · 3 comments
Labels
Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development non-issue Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release

Comments

@djfordz
Copy link

djfordz commented Feb 27, 2017

I have a customer site that Varnish is 503'ing on Category pages that have a too long X-Magento-Tags similar to this issue here: #6401.

Preconditions

  1. Magento 2.1.3
  2. CentOS 6
  3. Mysql Ver 14.14 Distrib 5.6.32-78.1
  4. PHP 7.0.16

Steps to reproduce

  1. Enable Varnish for page cache
  2. Add over 5000 categories greater than 4 levels deep each level with hundreds more categories
  3. try to goto category page

screenshot from 2017-02-27 10-22-30

Expected result

  1. Category Page displays

Actual result

  1. [Screenshot, logs]
    503 Varnish Cache Error
    screenshot from 2017-02-27 10-24-17
@djfordz djfordz changed the title Category X-Magento-Tags too long causing vanish to 503 Category X-Magento-Tags too long causing Varnish to 503 Feb 27, 2017
@ljrweb
Copy link

ljrweb commented Mar 20, 2017

I ran into this problem and I think Magento updated documentation to explain how to extend the parameter value in the varnish config.

http://devdocs.magento.com/guides/v2.0/config-guide/varnish/tshoot-varnish-503.html

@dcabrejas
Copy link

I have encountered this issue on a Magento site running on 2.1.5. Category pages containing a large number of products return aX-Magento-Tag header which is bigger than the size allowed by the HTTP specification.

We have implemented this workaround for now http://devdocs.magento.com/guides/v2.0/config-guide/varnish/tshoot-varnish-503.html

But this is not a solution, just a workaround because the http header size is still larger than the limit set by the HTTp specification.

@magento-engcom-team magento-engcom-team added G1 Passed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed and removed G1 Passed labels Sep 5, 2017
@magento-engcom-team magento-engcom-team added the Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed label Nov 14, 2017
@magento-engcom-team magento-engcom-team self-assigned this Nov 14, 2017
@magento-engcom-team magento-engcom-team added 2.1.x Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed non-issue Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release labels Nov 14, 2017
@magento-engcom-team
Copy link
Contributor

@djfordz, thank you for your report.
This seems to be correct Magento behavior. Please refer to the Community Forums or the Magento Stack Exchange site for advice or general discussion about this.
Otherwise you may submit Pull Request with the suggested changes.

magento-devops-reposync-svc pushed a commit that referenced this issue Feb 6, 2024
…ta3_03Jan23

[Hammer][Platform Health 247-beta3] ES8 Support Adobe Commerce 2.4.7 and 2.4.6
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development non-issue Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release
Projects
None yet
Development

No branches or pull requests

4 participants