- Issue created by @dotist
- 🇩🇪Germany marcus_johansson
The CSRF token must stay for security reasons, this sounds like a caching issue or that a session perhaps needs to start. We have it working for anonymous users on other websites.
Could you answer if you have bigpipe installed and what caching/cdn modules you might have installed, so we can try to replicate this.
- 🇩🇪Germany dotist
Thanks for your quick response! Indeed, after removing the CSRF token, loading the bot and then re-adding the token, the bot still works. So it's something to do with caching or timing.
The problem is in a local DDEV container using:
* Internal Dynamic Page Cache
* Internal Page Cache - 🇮🇳India anjaliprasannan
@dotist @marcus_johansson We have the chatbot working for anonymous user. I tried without the patch and its working for both authorized and anonymous user.