Skip to content
Contact Us
  • There are no suggestions because the search field is empty.

Learn about server-side caching in Membership.io Hubs

What server-side caching is, what gets cached, and what to do if caching issues happen

What can I use this for?

Caching helps web pages load faster by storing frequently used data on the server. This reduces the work the server has to do and speeds up content delivery.

This article explains how server-side caching works in Membership.io Hubs, which assets are affected, and what to do if caching-related issues happen.

What is cached on the server?

Membership.io Hubs store certain types of content to improve speed and efficiency. These include:

  • Styles and layout files (CSS) – These control how your pages look.

  • Interactive scripts (JavaScript) – These power interactive features.

  • Images and media – Pictures, icons, videos, and other visual content.

  • Fonts – The text styles used on your pages.

NOTE: Spotlight Search results are not cached to ensure they always show real-time data.

How long are files stored?

Cached files are stored for up to one year to improve speed and reduce server load. However, we have a system to ensure that updated files (like CSS and JavaScript) are always fresh when new changes are made.

Additionally, all cached content is securely delivered over HTTPS. Any HTTP requests are automatically redirected to HTTPS for security.

troubleshooting caching issues

If you make updates to CSS, JavaScript, or images but don’t see the changes, follow these steps to collect troubleshooting data for our support team:

  • Affected URLs – The web addresses of the files that seem outdated.
  • Response headers – Technical details about how the file is being served.

How to get the data for troubleshooting (Google Chrome)

  1. Right-click on the page and select Inspect.
  2. Go to the Network tab.
  3. Select the resource type (CSS, JS, etc.)
  4. Refresh the page to reload assets.
  5. Click on a specific asset, then copy the full Request URL and Response Headers under the "Headers" tab.

Capture request URL and response headers


TIP: Other browsers like Safari, Microsoft Edge, and Firefox have similar steps in their Developer Tools. Be sure to check their support documentation for guidance.

If you send a screenshot, make sure it shows the full file path and headers. Also, check if the issue happens on different devices or accounts.

More about server-side caching

  • Clearing the browser cache does not affect server-side caching.
  • If caching is working correctly, old files should not be served.
  • If a caching issue is confirmed, our support team will work with developers to investigate and clear the backend cache.

If you have any questions, feel free to ask our support team!