Expires Headers to nginx on Managed Wordpress platform
Ability to add Expires Headers to nginx on Managed Wordpress platform

Hello and thank your for the suggestion. At this time we do automatically configure the Managed WordPress platform for Expires Headers within nginx. Can you tell us more about any issues you may be experiencing? In addition, our dedicated Managed WordPress support team would be happy to help make sure there are not configuration issues causing the Cache-Control or Expires header to be overwritten. You can reach them directly by opening a ticket or chat from your Managed WordPress portal, or by calling 833-845-4527.
-
Admin[Deleted User] (Admin, Liquid Web) commented
Adam, it looks like there was a an issue with the configuration, but this has been adjusted and we believe the issue is resolved. If not, please be sure to let me know.
-
Admin[Deleted User] (Admin, Liquid Web) commented
Thanks for the follow up, Adam. I'm going to locate your request with out support team and pull in some additional help to see what we can do to alleviate this issue.
-
Adam commented
Hi Ani, thank you for the email. Both Pingdom and GTMetrix seem to be identifying expiration headers as an issue for our site. I did speak with the Managed Wordpress team but they could offer no solution at present. We currently utilize WP Rocket and have Varnish enabled. WP Rocket recommended the steps outlined by GitHub as best practices for NGINX, which your Managed Wordpress Support Agent informed me is not implemented on the Liquid Web managed platform. If you have any thoughts, we would greatly appreciate hearing more.
Thanks
Adam