Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author digitalpoint

    (@digitalpoint)

    It looks like you might have something on the backend (maybe a server-side caching system) that is trying to be smarter than it should be.

    It’s changing the cache control headers from what the plugin sets (“public, max-age=31536000”) to instead be (“max-age=31536000, must-revalidate”). It’s basically telling the end user’s browser that it’s not a public resource and that is must be revalidated every request.

    Thread Starter benklocek

    (@benklocek)

    Thank you! I’ll pass that on to them.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Caching Issue’ is closed to new replies.