[TAP5-468] ResponseCompressionAnalyzer should disregard the charset when comparing configured exluded mime types

• 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
• Assignee: Howard Lewis Ship
• Reporter: Paudi Moriarty
• Created: 26/Jan/09 08:50
• Updated: 27/Jan/09 01:04
• Resolved: 27/Jan/09 01:04

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.