Include message body in 302 responses

[michielvangendt]

Description

The 302 responses from the auth API 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 302 responses.

References

• My previous PR, sorry for not following up on this! Include message body in 302 responses #399
• 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).

• Similar fix in Next.js: Include message body in redirect responses vercel/next.js#25257
• Similar fix in Next.js: Include message body in redirect responses vercel/next.js#31886

[vercel]

Someone is attempting to deploy a commit to the Auth0 Team on Vercel.

A member of the Team first needs to authorize it.

[adamjmcgrath]

Thanks @michielvangendt

[adamjmcgrath]

Will put up a release after the holidays