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

Response is broken for String entities if charset is not explicitly specified

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.1.0.ER2
    • 7.1.0.DR13
    • REST
    • None

    Description

      If the response entity type is a String and the charset is not explicitly set, the String is converted to a byte[] using UTF-8. Since the default charset in HTTP is ISO-8859-1, the responses are invalid. Either, the conversion should use o.getBytes(StandardCharsets.ISO_8859_1) or the response charset should be set to utf-8 in that case.

      I recommend to set "utf-8" charset.

      This is violation of HTTP 1.1 specification, chapter "3.7.1 Canonicalization and Text Defaults":

      The "charset" parameter is used with some media types to define the
      character set (section 3.4) of the data. When no explicit charset
      parameter is provided by the sender, media subtypes of the "text"
      type are defined to have a default charset value of "ISO-8859-1" when
      received via HTTP. Data in character sets other than "ISO-8859-1" or
      its subsets MUST be labeled with an appropriate charset value. See
      section 3.4.1 for compatibility problems.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. RESTEASY-1565 Response is broken for String entities if charset is not explicitly specified

          • 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.
          • Resolved
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-9973 Upgrade RESTEasy to 3.0.22.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
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-9316 Decrease log level of "lack charset" warning message

          • Critical - To be worked on immediately following BLOCKER issues.
          • Verified

          Bug - A problem that impairs or prevents the functions of the product. RESTEASY-1622 Decrease log level of "lack charset" warning message

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

          Bug - A problem that impairs or prevents the functions of the product. RESTEASY-1620 resteasy.add.charset property is not described in RESTEasy documentation

          • 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.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. RESTEASY-1628 Response is broken for String entities if charset is not explicitly specified, Part 2

          • 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.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-9315 resteasy.add.charset property is not described in RESTEasy documentation

          • 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.
          • Closed

          Activity

            People

              rsigal@redhat.com Ronald Sigal
              mkopecky@redhat.com Marek Kopecky
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: