Suspense on soft navigation in production with Akamai CDN is blocking rather than showing fallback UI.

[muka-nakazato]

Goals

1. Please give me a workaround on how to use Suspense Stream with Akamai CDN.
2. I would like to continue to use CDN caching for RSC.

Summary

We run our self-hosted applications on EC2. We use Akamai's CDN.

I expect to see an immediate Suspense fallback when soft navigating, but actually the screen transition does not occur until the asynchronous request inside Suspense completes.

This problem is similar to #54667 .

I tried adding the configuration for Nginx described in the document, but it did not work.

https://nextjs.org/docs/app/guides/self-hosting#streaming-and-suspense

[icyJoseph]

Hi,

In my previous job, we had issues when working with Akamai too. We even ended up having higher TTFB because of the buffering, and when it was finally enabled, we noticed they had turned compression off...

All I can say is that, the team that managed Akamai for us at my old company, didn't get this one right the first, nor the second time.

I've tried through through the Akamai docs too, to try and figure out what has to be done but no luck. The only thing I could find, that's somewhat relevant, but still doesn't fix the issue, was this document, https://techdocs.akamai.com/edgeworkers/docs/process-response-bodies

Btw, have you verified, that requests that hit your origin (behind the CDN), do behave as expected?

[muka-nakazato]

@icyJoseph
Thank you for your response.

Btw, have you verified, that requests that hit your origin (behind the CDN), do behave as expected?

Yes, it works correctly if it does not go through a CDN.

e even ended up having higher TTFB because of the buffering, and when it was finally enabled, we noticed they had turned compression off...

Another team in our company had the same problem.
When they talked to the Akamai representative at that time, he responded as follows.

• rsc cache becomes unavailable.
• responses are no longer compressed

We are troubled because it is unacceptable that the cache will not be available on the CDN.
I heard that the team got around this by adding an extra hidden string to exceed the buffer capacity...