Server action calls are not failing on "413 Entity Too Large"

Feedback
1

Link to the code that reproduces this issue

To Reproduce

  1. Serve the server-actions-upload example behind a reverse proxy (i.e. Nginx or similar)
  2. Try uploading a file bigger than allowed by the reserve proxy
  3. Verify that an alert showing “Save success!” is shown

Current vs. Expected behavior

Awaiting a server action that returns a status code different than 200 should throw an error.

Provide environment information

Operating System: Platform: darwin Arch: arm64 Version: Darwin Kernel Version 24.1.0: Thu Oct 10 21:03:11 PDT 2024; root:xnu-11215.41.3~2/RELEASE_ARM64_T6020 Available memory (MB): 16384 Available CPU cores: 12 Binaries: Node: 22.13.1 npm: 10.9.2 Yarn: N/A pnpm: N/A Relevant Packages: next: 14.2.3 // An outdated version detected (latest is 15.1.6), upgrade is highly recommended! eslint-config-next: 14.2.0 react: 18.2.0 react-dom: 18.2.0 typescript: 5.4.5 Next.js Config: output: N/A :warning: An outdated version detected (latest is 15.1.6), upgrade is highly recommended! Please try the latest canary version (npm install next@canary) to confirm the issue still exists before creating a new issue. Read more - https://nextjs.org/docs/messages/opening-an-issue

Which area(s) are affected? (Select all that apply)

Server Actions

Which stage(s) are affected? (Select all that apply)

Other (Deployed), next start (local), next dev (local)

Additional context

Tested with NextJS 14. Tried creating the GitHub issue but it got reject automatically :man_shrugging: Server action calls are not failing on "413 Entity Too Large" · Issue #75663 · vercel/next.js · GitHub

2 Likes
2

Hi @atduarte, welcome to the Vercel Community!

You did the right thing by opening an issue on the Next.js repository. It got closed because you didn’t include a repository or public project where we can reproduce the results. For more information, see this comment.

If you need more help, please share your public repo or a minimal reproducible example. That will let us all work together from the same code to figure out what’s going wrong.

1 Like
3

Thanks, Anshuman! It includes a public repository link to next.js example folder that is sufficient to reproduce the issue :sweat_smile:

I guess I will copy that exactly to a new repo

2 Likes