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

Enabling trailingSlash will hang the request in RSC #34527

Closed
1 task done
huozhi opened this issue Feb 18, 2022 · 1 comment · Fixed by #34544
Closed
1 task done

Enabling trailingSlash will hang the request in RSC #34527

huozhi opened this issue Feb 18, 2022 · 1 comment · Fixed by #34544

Comments

@huozhi
Copy link
Member

huozhi commented Feb 18, 2022

Verify canary release

  • I verified that the issue exists in Next.js canary release

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 21.1.0: Wed Oct 13 17:33:24 PDT 2021; root:xnu-8019.41.5~1/RELEASE_ARM64_T8101
Binaries:
  Node: 14.17.0
  npm: 8.1.4
  Yarn: 1.22.15
  pnpm: 6.11.0
Relevant packages:
  next: 12.1.0
  react: 18.0.0-rc.0
  react-dom: 18.0.0-rc.0

Done in 0.60s.

What browser are you using? (if relevant)

Chrome 98

How are you deploying your application? (if relevant)

local testing

Describe the Bug

Testing https://github.com/vercel/next-rsc-demo with trailingSlash config enabled, RSC pages requests are hanged in dev mode and returning 404 in prod mode (next build + start).

Related to vercel/next-react-server-components#22 . WebServer doens't respond correctly.

Expected Behavior

RSC pages should work like normal pages with trailingSlash enabled, appending slash to the pathname if necessary

To Reproduce

  1. clone https://github.com/vercel/next-rsc-demo
  2. add trailingSlash: true in next.config.js
  3. run yarn dev
  4. request localhost:3000/rsc
@huozhi huozhi added bug Issue was opened via the bug report template. area: Concurrent Features and removed bug Issue was opened via the bug report template. labels Feb 18, 2022
@kodiakhq kodiakhq bot closed this as completed in #34544 Feb 18, 2022
kodiakhq bot pushed a commit that referenced this issue Feb 18, 2022
## Bug

Fixes #34527 

- [x] Related issues linked using `fixes #number`
- [x] Integration tests added
- [x] Errors have helpful link attached, see `contributing.md`
@github-actions
Copy link
Contributor

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 21, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant