Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-7983

RoleBasedSecurityFilter doesn't alter the Content-Type header

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 7.1.0.DR13
    • 7.1.0.DR9
    • REST
    • None

    Description

      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.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. RESTEASY-1563 RoleBasedSecurityFilter doesn't alter the Content-Type header

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-8639 Upgrade Resteasy to 3.0.21.Final

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified

          Activity

            People

              rhn-support-asoldano Alessio Soldano
              kanovotn Katerina Odabasi (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: