That would be correct for logged in.
Whereas, logged out on a fresh install, I get:
public, max-age=31536000, no-cache="Set-Cookie", s-maxage=1800, stale-while-revalidate, stale-if-error
You have configured CloudFlare to respect headers from origin so it cannot be. You can even disable it via the Developer mode button I showed you to appease. As Randy mentioned too, it could be a third party resource on your Invision Community install causing this so you would want to disable those as well.
That would be incorrect. As mentioned, something from your server is overriding Invision Community's default cache-control header thus CloudFlare is respecting this thinking that you set it on purpose and thus, not caching the page and thus, returning Bypass.
You will need to find out what is causing the cache-control to be set to no-cache and remove that on your server so that CloudFlare will cache the page and you will see the cf-cache-status set to a proper cache status (such as HIT or MISS).
I'm confused by your statement, all users would have the field present if the moderator in question has the ability to edit all user profiles. Could you please provide an example we can take a look at?
All set. I moved this to our sales teams' inbox so they will be in touch with you via email as soon as they can. There is a small backlog at the moment so there may be a slight delay just a warning 🙂 .
A 500 Internal Server Error is like a check engine light, it says something is wrong but not exactly what or where. You would need to obtain the server error log entry for the error here and if it is a server error, work with your hosting provider to resolve. If it is an issue with our core software, please post the error here and we can assist further.
Sorry, what exactly are you wanting to do here? We utilize different types based on what you are wanting to accomplish for your metadata. You can view source of the outputted HTML to see the different sets that are used in the software.
Please keep in mind that customizations are outside our scope of support so depending exactly what you're asking, we may need to move this to a different forum so you can receive assistance from other administrators.
I'm confused by what you mean here, if you are turning on/off development mode you would expect to see a change for cf-cache-status because that is exactly what you are doing.
cache-control in both instances are set to "no-cache" which is coming from your server and what you are investigating here.
Could you please confirm what my colleague mentioned? Unfortunately, we would not be able to confirm what you are stating here if we don't understand the original issue.
You would need to review your server headers being passed as mentioned several time now 😉 . Something from your server is sending a nocache header thus creating this problem.
You would need to ask the website owner because I would not know that. There are thousands upon thousands of reasons to use CloudFlare so maybe they simply don't want guest caching or haven't configured it yet.
Overview page -> Enabling "Development Mode" would disable all caching set by CloudFlare.
Dynamic would be their configuration in CloudFlare they likely have set caching to be Dynamic there (aka not cached by CloudFlare).
Browser Developer Tools -> Network tab -> (may need to refresh the page) -> click the page you're viewing, which is generally at the top and named as a variant of the URL you're accessing (in Chrome, should look like a blue page as in my screenshot).
As anything with running your own server, you have to know how you configured things and remove any conflicts. It really is simple (comparatively) but have to understand how things interact and how to test to get the desired result. If this isn't something you're wanting to perform, you can always hire a server administrator to do it for you or switch to our Cloud 🙂 .
You would need to ensure that cache-control is not being set by your server. As this is being set, it looks like it is overriding Invision Community's default control. Once you remove what your server is setting, the cf-cache-status header will fall inline with what you have configured in CloudFlare.
You will need to check your browser console tools to verify things are or are not working with each change you make.
OPCache and Redis are completely separate to this.
Unfortunately, you'll need to investigate with your hosting provider to ensure there isn't anything else set for caching headers on your server. As this is what is being returned in the headers: