Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: streaming while self-hosting must disable buffering #60943

Merged
merged 1 commit into from
Jan 21, 2024

Conversation

leerob
Copy link
Member

@leerob leerob commented Jan 21, 2024

Closes #54667

@leerob leerob requested review from a team as code owners January 21, 2024 16:08
@leerob leerob requested review from ismaelrumzan and StephDietz and removed request for a team January 21, 2024 16:08
@leerob leerob merged commit 5e80715 into canary Jan 21, 2024
29 checks passed
@leerob leerob deleted the streaming-deployment-docs branch January 21, 2024 16:52
@coltonehrman
Copy link
Contributor

@leerob This is awesome! We actually ran into the same issue, and instead used the X-Accel-Buffering header to disable buffering specifically for Next.js responses vs turning off buffering completely (which isn't recommended by nginx).

  async headers() {
    return [
      {
        source: "/:path*{/}?",
        headers: [
          {
            key: "x-accel-buffering",
            value: "no",
          },
        ],
      },
    ];
  },

@leerob
Copy link
Member Author

leerob commented Jan 23, 2024

Thank you @coltonehrman, updated: #61010

@github-actions github-actions bot added the locked label Feb 6, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 6, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Suspense in production is blocking rather than showing fallback UI
3 participants