vercel/next.js

POST request succeeds for pages with next dev

Open

Aperta il 21 lug 2022

Vedi su GitHub
 (6 commenti) (0 reazioni) (0 assegnatari)JavaScript (139.471 star) (31.066 fork)batch import
buggood first issuelinear: next

Descrizione

Verify canary release

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

Provide environment information

Operating System:
  Platform: darwin
  Arch: x64
  Version: Darwin Kernel Version 21.5.0: Tue Apr 26 21:08:22 PDT 2022; root:xnu-8020.121.3~4/RELEASE_X86_64
Binaries:
  Node: 16.14.0
  npm: 8.12.0
  Yarn: 1.22.17
  pnpm: 7.5.2
Relevant packages:
  next: 12.2.3-canary.15
  eslint-config-next: 12.2.2
  react: 18.2.0
  react-dom: 18.2.0

What browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

Describe the Bug

When you send a POST request to a page running with next dev, it succeeds with 200 status even though it fails with 405 status when running with next start

Expected Behavior

Non-GET/HEAD requests fail with 405 status code in the same way with next start

Link to reproduction

https://github.com/vercel/next.js/tree/canary/examples

To Reproduce

$ next dev

# on another terminal
$ curl http://localhost:3000 -X POST -v

The problem should happen on any apps.

Guida contributor

Tech stack
nextjsnodejsreact
Dominio
backend
Tipo issue
bug
DifficoltàQuanto dovrebbe essere impegnativa per un nuovo contributor.
3
Tempo stimatoTempo stimato per completare e verificare uno scope piccolo.
1-3 hours
Stato attivitàQuanto è probabile che la issue sia ancora attiva e reviewable.
fresh
ChiarezzaQuanto chiaramente la issue descrive problema, scope e risultato atteso.
mostly clear
Prerequisiti
Basic understanding of Next.jsHTTP request methods
Adatta ai principiantiQuanto la issue è adatta a contributor alla prima esperienza.
60
Direzione di ricerca
The issue is that POST requests return 200 during development (next dev) but 405 in production (next start). Investigate how Next.js handles HTTP methods in dev versus production. The likely area is the route handling in the dev server, possibly in files like `next dev server.ts` or the route resolver. Look at how methods are validated and see if there is a missing check for non GET/HEAD requests in dev mode. The reproduction is straightforward: run `curl X POST http://localhost:3000` while dev server is running. Review the source code to find where the method restriction is applied in production but missing in dev.