# HG changeset patch # User Guido Berhoerster # Date 1554145445 -7200 # Node ID 6bd8a649186d123f70baeb82061d4eefd8c51596 # Parent da5299097a48360da04ecf5603826aefd056cc93 Fix charset encoding in rewritten Content-Type header The charset encoding in the rewritten Content-Type header must be UTF-8 since that is what the original response body will be converted to. This fixes the garbled text seen when viewing feeds using charset encodings other than UTF-8. diff -r da5299097a48 -r 6bd8a649186d js/background.js --- a/js/background.js Mon Apr 01 20:39:08 2019 +0200 +++ b/js/background.js Mon Apr 01 21:04:05 2019 +0200 @@ -171,7 +171,7 @@ details.responseHeaders[contentTypeIndex] = { name: 'Content-Type', - value: `application/xml;charset=${contentType.charset}` + value: 'application/xml;charset=utf-8' }; return {responseHeaders: details.responseHeaders};