Home/ Questions/Q 6779743
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T16:25:26+00:00

RFC 2616 doesn’t specify whether a message-body is needed or not, which I interpret

  • 0

RFC 2616 doesn’t specify whether a message-body is needed or not, which I interpret as being optional. Is there any practical danger in omitting a message body?

For example, are there bugs (or features) in certain browsers that are triggered by a blank message body in a 302?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    It’s not needed. The RFC9110 spec on 302 however doesn’t forbid it as well.

    The server’s response content usually contains a short hypertext note with a hyperlink to the different URI(s).

    Note that it does forbid the message body for certain statuses, such as 204 and 304.

    A [204|304] response is terminated by the end of the header section; it cannot contain content or trailers.

    If the same were true for 302, then it should surely have been explicitly mentioned.

    As far as I know, all modern browsers ignore the message body of a 302 in response to a GET or POST and will directly go to the URL as specified in Location header.

    • 0