[TOMAHAWK-282] AddResource should use the current character encoding

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 1.1.2
• Assignee: Martin Marinschek
• Reporter: Mario Ivankovits
• Created: 19/Jan/06 19:19
• Updated: 07/May/06 01:43
• Resolved: 22/Jan/06 08:55

Description

In AddResource.writeWithFullHeader the current character encoding wont be used when instantiating the ResponseWriter.
This will encode the whole page even if the page is already in UTF-8 - where no further encoding should be done.

I maked it as blocker as this will break html-embedded-javascripts. All non-ascii characters were encoded and e.g. when alert() them the browser wont decode it.
But feel free to adjust the priority.

Attached you will find a patch which will take the response.getCharacterEncoding() - and the adjusted Test-Case.