Question 1

Laravel Page Cache vs Laravel's built-in cache?

Accepted Answer

Laravel Page Cache serves full HTML pages directly from disk, bypassing PHP entirely for cached requests, while Laravel's built-in cache stores data in memory/database and still requires app booting. Page Cache is faster for static pages but less flexible for dynamic content.

Question 2

How to exclude URLs with query strings from caching?

Accepted Answer

Extend the base middleware and override the `shouldCache` method to return false for requests with query strings, as shown in the 'Customizing what to cache' section. This allows you to skip caching for dynamic parameters.

Question 3

Best way to clear cache on deployment with Laravel Page Cache?

Accepted Answer

Add `php artisan page-cache:clear` to your deployment script, such as in Laravel Forge's Deploy Script, to automatically refresh cache after updates. This prevents serving stale content without manual intervention.

Question 4

Does Laravel Page Cache work with CDNs like Cloudflare?

Accepted Answer

Yes, but you need to configure the CDN to respect cache headers or serve static files from your server. Cache invalidation might require additional steps, such as purging CDN cache after clearing local files.

Question 5

How to cache only specific routes in Laravel?

Accepted Answer

Register the middleware in `middlewareAliases` and apply it selectively to routes using `Route::middleware('page-cache')`, as explained in the usage section. This avoids caching unnecessary pages.

Question 6

What happens to user sessions with cached pages?

Accepted Answer

Cached pages are served statically, so any session-dependent content (e.g., login status) won't be cached correctly. Avoid caching pages that require authentication or personalization, or use edge-side includes for dynamic parts.

Page Cache

What is Page Cache?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions