Uploaded image for project: 'RESTEasy'
  1. RESTEasy
  2. RESTEASY-1563

RoleBasedSecurityFilter doesn't alter the Content-Type header

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • 3.1.1.Final, 3.0.21.Final
    • 3.0.19.Final
    • jaxrs
    • None

      The response provided by the RoleBasedSecurityFilter, when a FORBIDDEN status is returned, provides a text description but leaves the negotiated content-type as is.

      This confuses our response processing as our 400 series errors return "application/problem+json" so we are using the Content-Type even when encountering these errors.

              rhn-support-asoldano Alessio Soldano
              kevinwooten Kevin Wooten (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: