New CDN feature caching SSE endpoints
moonflower-labs
PROOP

2 months ago

CDN is caching SSE endpoints despite Cache-Control: no-store

Enabling the CDN breaks SSE connections. The endpoint returns x-cache: HIT and a fixed content-length even with Cache-Control: no-store set. Fastly seems to be caching the initial response and serving it as a static snapshot, causing an infinite reconnect loop on the client.

Only fix right now is disabling the CDN entirely. Would be great to get either automatic exclusion for text/event-stream responses or path-based exclusion rules. Probably affects anyone using SSE or any streaming endpoint.

Solved

2 Replies

2 months ago

Thank you for the report. I've updated our caching rules to exclude text/event-stream. Please let me know if this is now fixed on your end.


moonflower-labs
PROOP

2 months ago

Excellent! Yes I can confirm everything is ok in my end. Thank you so much for the prompt response and action, much appreciated !


Status changed to Solved brody about 2 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...