Caching 500 Error Page?

Can you confirm which version of Quick Cache you’re running? The latest version (v140605) fixed this bug (although I see that I forgot to add that fact to the changelog): https://github.com/websharks/quick-cache/issues/175

I noticed when submitting this report that my version was a few releases behind. I have updated the plugin to the latest so it sounds like all should be well now.

Sorry to raise the alarm on something you already fixed!

No problem. ??

This is a great plugin indeed , easy to set up and works well ! btw Today I noticed the same issue with the plugin, the plugin seems to cache error pages … and I had to clear the cache . am wondering if this new version released or not.. am using Quick cache Version 140725

Thanks !!

Yes, the latest version of Quick Cache (v140725) includes the fix for that bug that was caching 500 Error Pages. If you’re still experiencing that problem, please provide me with a list of steps to recreate the issue in my test installation.

This is what I got when I was trying to fetch a page via Google Fetch and i had to clear the cache

the error was this

Fatal error out of memory (allocation 2015478) (tried to allocate 72bytes)…….

And I also noticed that the site is not automatically redirected to non-www version when the Quick cache is enabled, and both versions load on the browser, the www version is a bit old cached one though

I had to write extra lines of redirect rule on .htaccess file to fix it

Thanks

the error was this

Fatal error out of memory (allocation 2015478) (tried to allocate 72bytes)…….

Hmm. I haven’t seen Quick Cache cache that error since the fix was implemented in v140725, so it’s possible that Google Fetch was caching something and that clearing Quick Cache caused Google Fetch to recognize that it needs to refresh its own cache.

The next time this happens, please visit the site (while logged out of WordPress, so that you see the cached version) and then do “View Source” on your browser, copy the entire source, paste it into pastebin.com, and then share the link here for me to look at.

And I also noticed that the site is not automatically redirected to non-www version when the Quick cache is enabled, and both versions load on the browser, the www version is a bit old cached one though

I had to write extra lines of redirect rule on .htaccess file to fix it

Redirects are something you’d need to do in an .htaccess file; Quick Cache has nothing to do with redirecting to the non-www version, so if that’s not working, then there’s an issue with the rules in your .htaccess file.

Yea ik redirection has to do with .htaccess file but it had already done via Cpanel and it would redirect without any extra work in .htaccess file.. but that redirect doesn’t work when the Quick cache is enabled .. otherwise it does work…. however it is fixed with the two line of code in htaccess file, so no big deal.. I was just mentioning in case it helps someone

And I will do the other if it happens again

Thank you ??