ETag vs headers

[JesperBllnbm]

Describe the bug The API returns conflicting headers: ETag is provided for resource validation, but Cache-Control is set to no-store. This prevents the client from caching and validating the resource, rendering the ETag ineffective.

To Reproduce

1. Make a request to any endpoint returning ETag.
2. Observe the response headers: Cache-Control:"no-cache, no-store, must-revalidate".
3. Notice that caching is prevented despite ETag being present.

Expected behavior Either remove the no-store directive to allow caching with validation or remove the ETag header if caching is not intended.

Client details:

• OS: Any
• Browser: Any
• Version: Any
• Device: Any