|
Michael King
|
March 17, 2016 at 4:14 pm
By coincidence, I happened onto the isvarnishworking.com tool, which told me that Varnish was only partially working on my DreamHost “DreamPress” site. I see another post from 2014 where this came up, but it didn’t seem to reach a resolution. Digging into this with DreamHost support, they told that there were two cookies being set that were causing this. One was from Wordfence, the other is EE4:
ee_cookie_test=56e71a9268cc9; expires=Tue, 15-Mar-2016 20:09:54 GMT;
Max-Age=86400; path=/
Inactivating EE4 and turning off cookies in Wordfence allowed Varnish to work properly and made a measurable difference in load times. Hummm…
I understand the part about dynamic pages and excluding those from caches, but I don’t have an event on sale right now, so I don’t understand why there would need to be cookies pushed out of EE4, and it is not consistent with the explanation in the other thread about no-cache headers (or it doesn’t seems to be). The issue seems to be that the cookie has a 1-day life span to it. I can leave EE4 inactive for right now, but I have an event coming up soon so that’s not a long term solution.
Seems to me that you guys need to rethink what you’re doing here. Comments? Maybe you guys should call DreamHost and coordinate something?
|
|
Josh
|
March 17, 2016 at 4:44 pm
Other hosts use the no-cache headers. It turns out Dreamhost uses the cookies to determine whether or not to server from the Varnish Cache. Why would we need to rethink their decision?
|
|
Michael King
|
March 17, 2016 at 5:35 pm
I’ll forward your thoughts to DreamHost.
|
