[TAP5-2293] Closure minimizer produces invalid output on non-UTF-8 systems

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 5.4
• Fix Version/s: 5.4
• Component/s: tapestry-webresources
• Labels: patch
• Assignee: Jochen Kemnade
• Reporter: Jochen Kemnade
• Created: 24/Feb/14 08:26
• Updated: 28/Aug/14 08:15
• Resolved: 28/Aug/14 07:25

Description

When reading the minimization result from the Closure Compiler, the String is turned into an input stream using the platform's default encoding. If that is not UTF-8, the content that is sent to the browser is probably broken.

Issue Links

• is broken by: TAP5-2344 text assets (including modules and stacks) should assume a utf-8 charset, and incude ;charset=utf-8 in the response content type
• relates to: TAP5-2219 XML-Parsing broken if system encoding is not UTF-8