rsnext/packages/next/server/web/spec-compliant
Michiel Van Gendt d7062dddcc
Include message body in redirect responses (#31886)
# Description

The redirect responses do not contain a message body. This is in conflict with the RFCs (below) and causes Traefik (a reverse proxy) to invalidate the responses. In this pull request, I add a response body to the redirect responses. 

This PR is similar to https://github.com/vercel/next.js/pull/25257, it appears that there are some other locations where redirection is handled incorrectly in next.js.

# References
- https://datatracker.ietf.org/doc/html/rfc7230#section-3.3

> All 1xx (Informational), 204 (No Content), and 304 (Not Modified) responses must not include a message-body. All other responses do include a message-body, although the body may be of zero length.

- https://datatracker.ietf.org/doc/html/rfc7231#section-6.4.3

> The server's response payload usually contains a short hypertext note with a hyperlink to the different URI(s).

Co-authored-by: JJ Kasper <22380829+ijjk@users.noreply.github.com>
2021-12-16 05:41:43 +00:00
..
body.ts Implement Middleware RFC (#30081) 2021-10-20 17:52:11 +00:00
fetch-event.ts Fix TS error 2021-10-26 10:29:17 -05:00
headers.ts Implement Middleware RFC (#30081) 2021-10-20 17:52:11 +00:00
request.ts middleware: add request referrer support (#31343) 2021-11-15 19:52:44 +00:00
response.ts Include message body in redirect responses (#31886) 2021-12-16 05:41:43 +00:00