I would like to use Varnish before nginx+hhvm combo and I know that Varnish ignores any incoming request and outgoing response that has a cookie attached to it. Laravel creates a session cookie by default on every page it serves and to handle that most popular solution is to switch session driver along with the routes that depend on cookie (or laravel session monster for more specific solution). That works pretty fine with mostly static routing in pure laravel applications without dynamic, cms-based routes. So my question is - did anyone try to couple OctoberCMS with a Varnish instance and what would be the most sensible and CMS-friendly way to manage session cookie creation?

I will try laravel session monster today, but I am curious if there's a better way.