Jump to content

Dll

Clients
  • Posts

    1,164
  • Joined

  • Days Won

    4

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Forums

Events

Store

Gallery

Posts posted by Dll

  1. This isn't proving too useful to us as it currently works, unfortunately.

    As it only sets the cookie when the user logs in, it's setting very few as most users just stay logged in for a long period. It also doesn't pick up new registrations as they log in either.

    Also, although it's not as useful as the cookie detection method, the ip method isn't using the x-forwarded ip if that is used on the forum, so gives most users the same IP on our community.

     

  2. 5 minutes ago, Jim M said:

    Cache Rules are different than Page Rules.

    You're right. I thought they were used in combination with eachother, but looking at the docs, it is the equivalent of telling it to cache everything. 

    Quote

    Be aware that when you select Eligible for cache in Cache Rules, this is equivalent to cache everything cache level. If you do not enable eligible for cache, the expected behavior is the standard cache level present in Page Rules.

     

  3. 47 minutes ago, Jim M said:

    Just as a heads up, the cache rules are saying not to cache "these" but cache everything else 🙂 . Just want to clarify that so there is no confusion.

    I don't think they are for this use case though, as unless you tell cloudflare otherwise it won't cache html, which is what you're wanting it to do in this instance, I think? That needs a page rule to set it to cache everything. The cache rules is just about cache eligibility of the assets being loaded rather than specifically saying 'cache everything else', so won't over-ride the fact that html isn't cached.  (As far as I understand it)

    https://support.cloudflare.com/hc/en-us/articles/360021023712-Best-Practices-Speed-up-your-Site-with-Custom-Caching-via-Cloudflare-Page-Rules

    Quote

    Cloudflare does not cache HTML resources automatically. This prevents us from unintentionally caching pages that often contain dynamic elements. For example, the content on certain HTML pages may change based on specific visitor characteristics, such as authentication, personalization, and shopping cart information.

     

  4. Then I'd say it is as has been explained above - something else is setting the cache-control header which is over-riding the cloudflare side. You need to find what that is - it's highly likely something your host would need to change. 

    I'd recommend adding a / to the beginning of your uri rules on in the cache rule section as well, just in case not having them is causing a problem with it. 

  5. @marklcfc - I think you're actually only one step away from getting it working. The flow of the caching system in cloudflare is as follows:

    Could contain: Page, Text, Number, Symbol, Mobile Phone, Phone, Electronics

    While you've set up your rules for when not to cache, you've not actually told it when and what to cache. For that, you need to make a page rule for your url - with a wildcard, so it happens on every page. (eg https://www.foxestalk.co.uk/*)

    Then you need to select cache level and chose cache everything. 

    Could contain: Page, Text, File

    Then once you've saved it, give it 30 seconds and you should have a fully working page cache for guests.

×
×
  • Create New...