Uploaded image for project: 'Commons - HTTP Framework'
  1. Commons - HTTP Framework
  2. CHF-208

Provide support for GET and HEAD request to include a payload (entity)

    XMLWordPrintable

    Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 21.0.0, 22.0.0, 23.0.0, 24.0.0, 25.0.0, 26.0.0
    • 26.0.0, 24.0.13, 25.0.3
    • http-grizzly, http-servlet
    • IG being used to proxy an application that has behaviour that is dependent on GET requests providing a payload (entity) in the request.

      Description

      For both GET and HEAD, rfc7231 has:

       A payload within a GET request message has no defined semantics;
       sending a payload body on a GET request might cause some existing
       implementations to reject the request.
      
       A payload within a HEAD request message has no defined semantics;
       sending a payload body on a HEAD request might cause some existing
       implementations to reject the request.
      

      Even though these payloads have no defined semantics, CHF should still honour these requests having a payload (entity) if it is presented and not remove them as part of creating the internal Request representation.

      This leaves TRACE as the only request that does not need a support a payload, from the RFC:

      A client MUST NOT send a message body in a TRACE request.
      

        Attachments

          Issue Links

            Activity

              People

              markdr Mark de Reeper
              markdr Mark de Reeper
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: