Cache Lookup `vary-by-query-parameter` not working

[oskrabanek]

Report

Cache Lookup policy should by default cache separately by all query parameters as stated in the documentation at vary-by-query-parameter. Even when specifying the caching with vary-by-query-parameter element the caching still doesn't respect the caching. I would expect the query would be reflected in the cache key, which is not e.g. 3_apimtestwe.azure-api.net.23_static-api_static-api-uat;rev=1.38718_GetTenantApplicationsFooter.37979_8_https_graphql-we-uat.services.ori_443_/tenants/ee/applications/footer

Expected Behavior

Cache would take into account the query parameters.

Actual Behavior

CacheLookup with vary-by-query-parameter should store backend request separately based on the query parameters defined.

Steps to Reproduce the Problem

1. Define /tenants/{tenant}/applications/footer?lang={lang} endpoint
2. Define policy with <cache-lookup> with <vary-by-query-parameter>lang</vary-by-query-parameter> element
3. Call the endpoint with different lang values
4. The cache should contain multiple entries differing based on the query parameter

Logs from self-hosted gateway

None

Self-hosted Gateway Version

2.2.0

Deployment

Self-Managed (YAML/Helm)

Platform

Microsoft Azure

Kubernetes Version

1.25

Anything else?

The issue is reproducible on Managed API Management as well.

[tomkerkhove]

Created an internal bug, thanks for reporting

[akarshroot]

Hi Tom Kerkhove (@tomkerkhove) Is there any update on this? Still facing this issue.
Ondřej Škrabánek (@oskrabanek) Did you find any workarounds ?

[oskrabanek]

Akarsh Tripathi (@akarshroot) We've started to use the header instead

<cache-lookup allow-private-response-caching="true" downstream-caching-type="private" must-revalidate="false" vary-by-developer="false" vary-by-developer-groups="false">
    <vary-by-header>Accept</vary-by-header>
    <vary-by-header>Accept-Charset</vary-by-header>
    <vary-by-header>Accept-Language</vary-by-header>
</cache-lookup>

[akarshroot]

Ondřej Škrabánek (@oskrabanek) Thanks! Although i cannot do the same as i have multiple params.