It's important we hit file-server as little as possible as it currently blocks the thread each time it serves a file. Broadly we cache in NGinx any requests not routed through /api/* which covers most static files but there are exceptions.
One exception we know about is the debate conversation page which is loaded at least once per participant - this sets a cookie in the header which breaks the caching in NGinx.
Investigate how we might enable the debate conversation page to be cachable
This could be removing the cookie if not needed, allowing NGinx to ignore cookies when caching if this is safe (may want to do this on a file-by-file basis)
Determine if any there are any other files that should be cached but aren't
It's important we hit
file-serveras little as possible as it currently blocks the thread each time it serves a file. Broadly we cache in NGinx any requests not routed through/api/*which covers most static files but there are exceptions.One exception we know about is the debate conversation page which is loaded at least once per participant - this sets a cookie in the header which breaks the caching in NGinx.