-
Notifications
You must be signed in to change notification settings - Fork 27.5k
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
Unclear error message when deploying to Vercel #27696
Labels
bug
Issue was opened via the bug report template.
Comments
5 tasks
kodiakhq bot
pushed a commit
that referenced
this issue
Aug 2, 2021
This ensures we enforce a limit for `source`/`destination` values on rewrites, redirects, and headers since these being too long can affect routing performance. Closes: #27696
Thanks for the fast turnaround, @ijjk! |
flybayer
pushed a commit
to blitz-js/next.js
that referenced
this issue
Aug 19, 2021
This ensures we enforce a limit for `source`/`destination` values on rewrites, redirects, and headers since these being too long can affect routing performance. Closes: vercel#27696
This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What version of Next.js are you using?
11.0.1
What version of Node.js are you using?
n/a
What browser are you using?
n/a
What operating system are you using?
linux (on vercel)
How are you deploying your application?
Vercel
Describe the Bug
See getsentry/sentry-javascript#3851.
When deploying their app to Vercel, one of our users is getting the error message:
We're unable to replicate this behavior, and are having trouble debugging their issue, in part because the error message they're getting isn't totally clear. Specifically, what should not be longer than 4096 characters?
Expected Behavior
Ideally, the error message would:
a) Explain what value is too long (what it represents, where it was found, etc)
b) Perhaps even give the first n characters of said value, for easier pinpointing of the problem
To Reproduce
Do something which triggers this error message.
For what it's worth, I've tried to find any version I could of this error in both the nextjs and vercel codebases, and have been unable to. The only similar issues/discussions I could find were vercel/vercel#5940 and vercel/vercel#4799, but neither one addressed this particular error message.
The text was updated successfully, but these errors were encountered: