How to handle urls that sometimes contain a querystring

[JonoB]

Its unclear to me how to handle urls that may sometimes contain a query string.

For example, if you have a /blog url, and then pagination (/blog?page=2, /blog?page=3), etc.

Unless I'm missing something, this package cannot handle query string's at all - it looks like only the actual uri is cached, and not the query string. Hence the example on the front page of the package demonstrating how to exclude routes that contain a query string.

However, even if you implement that method, then the main /blog page will still get cached, which means that nginx will automatically serve up that same page for anything with a query string.

I think there are 2 options here:

• Don't implement caching at all for the /blog route
• Somehow include query strings in the page-cache files (is this even possible)?

[jberculo]

It would not be very difficult to add these to the file name. like blog-page-2 and blog-page-3. However, you would also need to change the htaccess to make this work. It's probably doable, but not trivial.

The caveats here are of course search pages or other pages with get requests that change a lot. Those would also generate a cached page per query string.

Added to that, it would make your site vulnerable. An attacker could fill your disk with just calling a page with random query strings.

In the end I opted to use Spaties Response Cache. This still hits your application, but combined with the free tier cloudflare service it comes close. https://github.com/spatie/laravel-responsecache

[Ozerich]

It might helps you

NGINX Config:

set $cacheFileName $uri;
if ($query_string != ''){
    set $cacheFileName $uri?$query_string;
}

location / {
    try_files /page-cache/$cacheFileName.json /index.php?$query_string;
}

[JosephSilber]

Its unclear to me how to handle urls that may sometimes contain a query string.

This package, by design, does not handle query strings.

---

For example, if you have a /blog url, and then pagination (/blog?page=2, /blog?page=3), etc.

I would change the URL structure, so that it's /blog/page/2, /blog/page/3.

Many sites use this, and it's what Wordpress ships with by default.

---

Laravel's built-in paginator unfortunately uses the query string by default.

You can now subclass the built-in paginator, so you can change the generated links to use /page/{num}.