allowed_query_strings_urls for full measure static caching

[stuartcusackie]

I just realised that the allowed_disallowed_query_strings options have no effect with full measure static caching. It presents a problem for me as my site needs to ignore gtm_ referal queries but allow collection pagination queries. I don't understand the technicalities of why these options don't work with nginx, but I wonder if there is a workaround.

In reality I'm never going to be using a Google campaign to link to a paginated url, i.e. it makes no sense for my Google ads to link to mywebsite.com/?page=2. So if the these options will never work for full-measure static caching then I wonder if there could be a new option in the static caching config called allowed_query_strings_urls.

`ignore_query_strings' => true,
'allowed_query_strings_urls' => [
  '/blog'
]

This way GTM query strings would be ignored on all pages, except for the '/blog' page, where I need pagination.

Is this possible or am I missing something? Thanks!

Also, it would be nice to have an additional comment in config/static_caching.php to remind us that the current options are incompatible with full measure.

Related ideas / issues:

#1306
statamic/cms#11142 (comment)

[indykoning]

You're right, it seems to be due to the overridden getUrl function here
https://github.com/statamic/cms/pull/10701/files#diff-1b0f87654d2a70e3258e1fd076d282ca357aa67337937db29165b1de7d87cb14R269-R295

it does not filter out the url parameters according to the allow/disallow list

[ryanmitchell]

They have no effect as when you use full static caching the request is handled by nginx, so Statamic has no control over stripping the URLs. Then there is also the issue of the order the query strings appear as nginx treats them as different urls when the order is different.

If you want these features I'd suggest switching to half cache as the speed different is negligible now and you get the benefits of all the requests still running through PHP so features like this can work.

[indykoning]

You're somewhat right there, however when nginx cannot directly find the file it will still be handled by Statamic so the rules would still be able to be applied (sure it won't be nginx serving directly fast, but as you say fast enough)

As a user of cloudflare or another similar proxy things like sorting the query parameters can be handled there.

Due to CDNs capabilities i must say full cache is quite superior to half.

Since statamic/cms#11430 is missing in Statamic, https://github.com/statamic/docs/pull/1602/files is the only way to tell a CDN to cache the cached page. But that requires full page caching.
Full saves on server load and speed:

• Half: bootstrap ~100ms, page from cache: 50ms, total: 150ms
• Full: page from cache: 60ms
• Full + CDN: page from cache: 30ms