Caching difference between dev and prod
-
The dev environment site has no problems getting the most recent Instagram post even without configuring the plugin to automatically clear the cache. However, the prod environment only gets the updated Instagram post if I manually clear the cache. I’ve configured the prod environment to automatically clear the cache, but that doesn’t seem to work.
There is an infrastructural difference between our dev and prod environments. The prod server is behind an Apache httpd reverse proxy server.
I did a moderate review of the Apache httpd 2.4 documentation, and I’m pretty convinced that the reverse proxy is obeying / passing through whatever headers it receives from production server (also Apache httpd v 2.4)The documentation also seemed to say that the reverse proxy should not change any of the headers having to do with caching, so am fairly sure the reverse proxy is just passing whatever headers from the production server to the client.
I also did not see any documentation within mod_proxy, etc., to selectively override and caching headers.
I still don’t think it is the reverse proxy in front of the prod server given that other content that has been updated immediately shows up, but wanted to mention the fact that another difference between Prod and Dev is the proxy.
All of this said, is there a reason why the Instagram feed would pull the new IG posts for dev without needing a manual cache clear, but for prod, I have to manually clear the cache?
The topic ‘Caching difference between dev and prod’ is closed to new replies.