When your GET endpoint depends on a cookie value and you are using a page cache like NGINX together with
Redis, you could run into caching issues. Why? NGINX mostly uses the query parameters as cache key and also
hits the cache even the cookie values changed. Two possible solutions are either to switch to a non-GET verb
or using this property. This allows you to define a list of cookie keys which should be sent as _httpCookieInvalidate
parameter and the cookie value base64-encoded.
When your
GETendpoint depends on a cookie value and you are using a page cache like NGINX together with Redis, you could run into caching issues. Why? NGINX mostly uses the query parameters as cache key and also hits the cache even the cookie values changed. Two possible solutions are either to switch to a non-GETverb or using this property. This allows you to define a list of cookie keys which should be sent as_httpCookieInvalidateparameter and the cookie value base64-encoded.