Uploaded image for project: 'Tapestry 5'
  1. Tapestry 5
  2. TAP5-468

ResponseCompressionAnalyzer should disregard the charset when comparing configured exluded mime types

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 5.1.0.0
    • Fix Version/s: 5.1.0.0
    • Component/s: tapestry-core
    • Labels:
      None

      Description

      Adding "application/json" to the configuration for ResponseCompressionAnalyzer doesn't work because it's compared for equality to "application/json;charset=UTF-8".

      The charset should probably be ignored.

        Attachments

          Activity

            People

            • Assignee:
              hlship Howard M. Lewis Ship
              Reporter:
              pmoriarty Paudi Moriarty
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: