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

Varnish caching issue #55

Open
Amadeco opened this issue Dec 11, 2024 · 0 comments
Open

Varnish caching issue #55

Amadeco opened this issue Dec 11, 2024 · 0 comments

Comments

@Amadeco
Copy link

Amadeco commented Dec 11, 2024

Hello @magenx,

Thank you for this repository,

I am using this one for quite a long time, but I would like to ask you something,

I was activating your solution for drilling layered navigation by bots (extra_protect.conf) but the condition (your regex) was sometime working sometime not.

The issue seems to be related to varnish which can cache the HTTP request from only ONE side (no difference between robots or visitor by default) with the default configuration of Magento 2 (VCL config files).

include conf_m2/extra_protect.conf;

As HTTPS (TLS/SSL protocol) is a mandatory now, every request pass by port 443 by default

Copie de unnamed

So I was wandering why some portions of the code from conf_m2 directories to the port 8080 was not added to the server port 443 in the config file of default sites-available magento2.conf. In particular, error_page.conf and some of this one : extra_protect.conf.

I did a test with an extension which can allow me to change the user-agent from my navigator and with the moving of the config files to the right server config, it is working.

As I am not knowledgeable in this domain, let me ask you for your expertise for this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant