Mamba Store API Caching

Mamba accelerates WooCommerce Store API reads while safeguarding user data. It caches safe GET endpoints for catalog data and applies a short per-cart microcache to smooth bursts during cart activity without risking cross-user leakage.

What’s Cached

  • Safe GET endpoints that serve catalog data such as products, categories, tags, and collections.
  • Guest requests without a cart receive normal catalog cache with ETag support for fast 304 Not Modified responses.

Per-Cart Microcache

  • When a visitor has a cart, Mamba applies a very short, seconds-level per-cart microcache.
  • This smooths bursts of rapid API calls (for example, UI polling) while keeping the cache user-scoped.
  • Cart or checkout mutations instantly clear the relevant microcache entries.

What’s Not Cached

  • Logged-in sessions
  • Non-GET requests
  • Sensitive Store API endpoints related to cart, checkout, or account state

Headers and Revalidation

  • ETag support is included so returning clients and proxies can revalidate responses with 304 Not Modified.
  • Vary headers are scoped to meaningful tokens such as Accept-Language and Accept-Encoding, plus geolocation when applicable. This avoids unnecessary high-cardinality keys.

Copyright 2025 - Mamba

Mamba mascot