Performance
Enabling HTTP Cache for Logged-in Users
By default, Shopware disables the HTTP cache for authenticated users to ensure that personalized content remains private. While enabling this can significantly improve performance, doing so without proper safeguards can lead to data security risks.
The Challenge: Personalized Data & Security
Shopware generates a "cache hash" to determine which stored content to serve. Typically, this hash is based on broad parameters like Rule IDs, Currency, and Tax State.
The Risk: Standard Shopware cache hashes do not include the Customer ID.
In a B2B environment, if two customers share the same rules and currency, the system might accidentally serve Customer A a cached page containing Customer B's specific prices or private account details. This poses a significant data protection (GDPR) risk.
Our Solution: Secure B2B Caching
To allow you to benefit from high-speed performance without compromising security, the B2Bsellers Suite includes native logic to handle per-customer caching safely.
This feature is enabled by default within the suite. Our system automatically extends the standard Shopware HTTP cache hash to include the Customer ID whenever a user is logged in.
Unique Cache Versions: Every logged-in customer receives their own unique cache entries.
Data Privacy: This prevents the accidental leakage of personalized B2B data between different user accounts.
Out-of-the-Box Security: You can utilize the Shopware HTTP Cache for logged-in users immediately, as our suite manages the secure hash generation in the background.
Configuration & Settings
While the feature is active upon installation, you can find the toggle in the Shopware Admin should you ever need to adjust it:
Navigate to B2B Settings > Core Settings.
Locate the setting: "Enable customer specific caching".
Ensure this is set to Enabled to maintain secure, high-performance caching.
Last updated
Was this helpful?