You should not be caching restricted pages on the server side, it is very insecure and a problem waiting to happen. Content caching should only really be used for somewhat static public pages.

willrowe said:

You should not be caching restricted pages on the server side, it is very insecure and a problem waiting to happen. Content caching should only really be used for somewhat static public pages.

These pages are not restricted, they are completely the same for logged out and logged in users. But problem is when a page is cached while a user is logged in, if you know what I mean.

That's still a dangerous line to walk, if you ever add user specific data down the road you could end up with a breach. Regardless, the session data should not be cached. It may be a bug with the package, maybe submit an issue to the Github repository. I've actually recently released a package for response caching in Laravel if you want to check it out and see if it does what you're looking for.