issacchua

Hi Marko,

Thanks for your reply.

I have uploaded a video to show you what I am seeing on my browser (Chrome version: 91.0.4472.77).

https://drive.google.com/file/d/1jpj5ZePW6RFoJb8SWl4WFXPLYDG1wpJn/view?usp=sharing

I have tried running incognito mode on Google Chrome, Edge, or on Mobile Chrome, all of them are having the same issue.

Hi Marko,

Thanks for your reply. I have seen the other posts that talk about compression stuff but it is not my case here.

To iterate, with my previous PHP version 7.4.7(I believe), it is working fine but after I upgrade to PHP version 7.4.19 along with the nginx up to 1.20, it is not behaved as before. I am not sure if that has anything to do with this issue.

My server is running nginx. I have not used any other gzip or zlib compression or other plugin. W3 Cache is the only plugin that I used, the configuration is the one that generates by W3 Cache.

You can check it out this link below:

https://www.test.menusifudemos.com/

Type other URLs that will cause 404, ex: https://www.test.menusifudemos.com/blahblah

Please note that the second time you revisit the same link, the page can be displayed properly. It only occurs on the first time (when the page cache is missed).

Thanks a lot Marko!

It actually doesn’t make sense.

Something is wrong with it. My CSS/JS/HTML are all compressed with gzip when I run the inspection on the requests.

Not sure why unsetting them (gzip compression) in the W3 cache options can fix the problem I had…

Hello, I think I have found the culprit.

It was the Browser Cache > Enable HTTP (gzip) compression that is causing the issue.

If I disable it, then it will work. If I enable it, then it will show the broken page that can’t even load (basically just blank page and freeze there).

The funny part is, I don’t even change the settings on the nginx.conf (my nginx.conf doesn’t get overwritten to protect the value) and simply turning that off, things will work correctly.

May I know if that is the right way to temporarily fix such problem? Any potential drawback for doing so? Thanks again.

Hi, yes, I am facing this weird issue.

When the page is missed, the whole webpage fails to load. However, the page cache is generated and if you reload the page, you can display the webpage from the cache correctly. I am still looking what exactly causing this.

I am happy to provide more information if you need. As for now, I will just keep trying to identify this issue.

BTW, like the OP posted, I am having no such issue on 7.4.x version before (I can’t remember the previous version) but when I upgrade my PHP to 7.4.19 (the latest version on Amazon Linux 2), I am getting this isuse.