Title: Plugin Caching
Last modified: September 1, 2021

---

# Plugin Caching

 *  [andrewapd](https://wordpress.org/support/users/andrewapd/)
 * (@andrewapd)
 * [4 years, 9 months ago](https://wordpress.org/support/topic/plugin-caching-2/)
 * The knowledge base [article ](https://onelogin.service-now.com/support?id=kb_article&sys_id=7b3992dedbd47410fe39dde748961950)
   has a note at the bottom:
 * > Note: WP Engine and similar WordPress hosts cache plugins and protect the wp-
   > login.php view. Contact your WordPress host to disable the cache for this SAML
   > plugin and to also allow external HTTP POSTs to wp-login.php.
 * We use WP Engine and have discussed this request with their support team. They
   understood what is meant by unprotecting wp-login.php, however they need more
   information regarding caching plugins.
 * Here is the relevent excerpt from our online chat with them:
 * > AGENT (Jon K.): I believe the wp-login.php protection refers to our default
   > login protection that we have enabled on sites and I can disable that, but 
   > I’m not seeing specifics listed anywhere for the cache exclusions. We can add
   > cache exclusions for pages, cookies, or URL arguments, but we need to know 
   > which ones to exclude – we wouldn’t know off the top what should be excluded
   > to make that particular plugin work with our caching, so it would be best if
   > they could provide you with a list of pages or URLS that should be uncached.
   > USER: It seems they think you cache plugins themselves?
   > AGENT (Jon K.): That’s the phrasing they use but that’s not really how our 
   > caching works – we cache pages in our varnish cache but not things like plugin
   > files, unless they’re static assets like CSS or JS.
   > USER: that makes sense.
   >  USER: The plugin is “OneLogin SAML SSO” USER: I wonder
   > if it operates within it’s own folder
   > AGENT (Jon K.): yep, it looks like wp-content/onelogin-saml-sso for that one,
   > but excluding files or ‘pages’ within that directory wouldn’t be likely to 
   > have the desired effect. For instance, /wp-content/plugins/onelogin-saml-sso/
   > onelogin_saml.php is the URL for what looks to be the main PHP file for the
   > plugin, but nobody would be accessing that page directly – it’s more likely
   > there are pages with a certain cookie present or URL structure that the plugin
   > uses that should be excluded from caching, we’d just need to know exactly what
   > those are.
   >  AGENT (Jon K.): As far as the login protection goes, I’ve disabled
   > that setting on the site from here so that shouldn’t be causing any conflicts.
 * Can you please explain further what they need to change?
    -  This topic was modified 4 years, 9 months ago by [andrewapd](https://wordpress.org/support/users/andrewapd/).
    -  This topic was modified 4 years, 9 months ago by [andrewapd](https://wordpress.org/support/users/andrewapd/).
      Reason: Remove URL

The topic ‘Plugin Caching’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/onelogin-saml-sso.svg)
 * [OneLogin SAML SSO](https://wordpress.org/plugins/onelogin-saml-sso/)
 * [Support Threads](https://wordpress.org/support/plugin/onelogin-saml-sso/)
 * [Active Topics](https://wordpress.org/support/plugin/onelogin-saml-sso/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/onelogin-saml-sso/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/onelogin-saml-sso/reviews/)

 * 0 replies
 * 1 participant
 * Last reply from: [andrewapd](https://wordpress.org/support/users/andrewapd/)
 * Last activity: [4 years, 9 months ago](https://wordpress.org/support/topic/plugin-caching-2/)
 * Status: not resolved