Imagine that we want to increase the speed of our site responses. Of course, we will use cache. We can cache requests to the database, we
can cache views, but we can also cache the whole response. But the response should have some dynamic parts. For example, if we have forms
we should provide csrf-tokens for them.
Let’s create use Laravel Middlewares for it. For example, CachingMiddleware:
This command creates our new middleware in the app/Http/Middleware folder. First of all we need to define controller actions that
we want to cache. I’ve made a collection cachedActions, where the controller class is the key, and actions will be values:
Next, we need to define the main method of every middleware, handle():
Let’s take a closer look to the getResponse() method. First of all we check if we need caching. For example, on local machine or if
the current route is no specified in the cachedActions array we simply return the response as it is. In the cachedActions we can
tell to cache the whole controller or some specific actions.
Next, if the current route needs to be cached we create a cacheKey, which is simply the current path of the route. So every route has
it own unqiue cache key.
And that is our caching middleware. It is very simple. Interesting things come when we want to have some dynamic parts in the reponse.
Add Dynamic Content
Let’s define the types of dynamic content that may occur in the response. I’ve defined only two: a string and a rendered view. Then we
need to create some placeholders, that will be replaced with the real content:
In the code above I’ve defined a protected property $replaceData. It has to sub-arrays: one for the csrf-token for our forms on the site,
and the second for the user cart info, that will be displayed in the site header.
Next, we need methods to replace different dynamic content from the cache with the real data: replaceViewContent
and replaceStringContent. The first one will render the view and then replace the specified placeholder with it, and the second one
will simply do str_replace:
Notice that there is a common pattern in these methods names: replaceTYPEContent. It is done to call them dynamically, depending on the
replace content type. Now we need some base method, that will iterate through the replaceData and replace the dynamic content:
Lastly, we need to update our handle() method:
Now our caching middleware is ready. But how we are going to replace, for example, csrf-tokens? Where to put tokens in the view?
Example with token
We can use meta tag in the main layout and put the placeholder there:
Next, we need to tell our middleware the real token for the replacement. For this purpose we can define a new method initReplaceData and
call it in the constructor:
@ 2018. All rights reserved.
If you've got any feedback, comments or just want to chat you can get in
touch via Twitter or email.