Handling https and caching for small interactive sites with caddy?

Hi everyone,

I’m running a small interactive site behind caddy and overall it’s been great, but I’ve hit a few questions around fine-tuning the setup. While working on a word-based game at letters boxed, I started noticing some edge cases with aggressive caching and https behavior, especially when users refresh quickly or revisit the site after a short break.

I’m trying to figure out the best balance between performance and correctness. In particular, I’m unsure about optimal cache-control headers for frequently changing game state, how to avoid stale responses when using caddy’s defaults, and whether there are any gotchas with automatic https that might affect lightweight interactive apps.

For those of you running similar small apps or games on caddy, how do you usually approach caching and header configuration to keep things fast without breaking user experience?

Would appreciate any guidance or examples from real setups. Thanks!