Varnish Cache Issue

Hi,

I originally wanted to use your plugin for my website, but after the caching issue (as talked about on this ticke: #3398924 within your website) I stopped using it and decided to not renew my Bundle since I wasn’t using it, and I wasted my money. You said in the last post within that ticket that you thought you had fixed the issue, but it never corrected the problem, so I used it for a total of a few weeks before uninstalling it.

I recently installed your plugin again to give it a try on the free version, but the issue with the Varnish Cache still remains. I host with Dreamhost and they use server side caching via Varnish Cache. I would really like to be able to use your plugin, but I still cannot with this issue because your plugin keeps my caching plugin from working with the cookies that it puts onto the website. My website loads around 2 seconds and as soon as I activate your plugin my website takes 10 or more seconds according to GTMetrix because the cookie in your plugin doesn’t allow my website to cache.

Can you please take another look at this issue. I would love to be able to use your plugin, but I need this issue to be resolved before I give it another try.

Thank you,

My Original Ticket Comments:

“`My website is not caching, as alerted and explained on my Site Health Status. I contacted my hosting provider (DreamHost), and after 3 hours of chatting back and forth, we figured out via a process of elimination that the Awesome Support plugin is the issue.

The explanation from my hosting provider is the following: “The plugin is generating session_cookies that set no-cache headers when running a cURL. The idea is to avoid that, developers should like to avoid setting no-cache headers for sites to be successfully cached.”`”

and

“`There is no debug.log file being created. – According to DreamHost Tech Support “Furthermore, the debug log only tracks WordPress errors – if the issue is a plugin conflict with server caching, that is very likely not going to appear in the debug log.”

DreamHost Tech Support also said “From what we’re seeing, the plugin-cache conflicts are PHP sessions or cookies – in most cases, the plugin provider should have details regarding that and/or any fix/recommendations for those as well.”

and

“It’s simply that the cache isn’t running and we’ve identified that the issue was caused by conflicts with the plugin in question’s PHP sessions or cookies.`”