Skip to content

Crawler or Google prerender bot requests do not buffer responses #2785

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

Open
pieh opened this issue Mar 26, 2025 · 0 comments
Open

Crawler or Google prerender bot requests do not buffer responses #2785

pieh opened this issue Mar 26, 2025 · 0 comments
Labels
Next.js e2e test failure Errors identified through the Next.js repo e2e tests

Comments

@pieh
Copy link
Contributor

pieh commented Mar 26, 2025

  ● streaming-ssr-edge › should not stream to crawlers or google pagerender bot

    expect(received).toBe(expected) // Object.is equality

    Expected: 1
    Received: 2

      86 |       flushCount++
      87 |     })
    > 88 |     expect(flushCount).toBe(1)
         |                        ^
      89 |     const html = await res1.text()
      90 |     const body = await getNodeBySelector(html, '#__next')
      91 |     // Resolve data instead of fallback

      at Object.toBe (e2e/streaming-ssr-edge/streaming-ssr-edge.test.ts:88:24)

Data

The following is parsed automatically by the Next.js repo e2e test report generator.

test: streaming-ssr-edge should not stream to crawlers or google pagerender bot
reason: Crawler or Google prerender bot requests do not buffer responses

@pieh pieh added the Next.js e2e test failure Errors identified through the Next.js repo e2e tests label Mar 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Next.js e2e test failure Errors identified through the Next.js repo e2e tests
Projects
None yet
Development

No branches or pull requests

1 participant