JS output filter silently truncates UTF-16 encoded external .js files
Bug #488825 reported by
e.fryntov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
psiphon |
Fix Committed
|
High
|
e.fryntov | ||
2.4 |
Fix Committed
|
Undecided
|
e.fryntov |
Bug Description
Psiphon applies charset transcoding only to (x)html documents. JS documents have to be transcoded the same way in order to apply search&replace regex rules:
server -> get JS document original encoding -> UTF-8 -> search&replace -> back to JS document original encoding -> browser
Also, we need to to extend the encoding detection by checking for BOM in case there is no charset info neither in the response header nor in the document body(there is no meta tags in JS documents for example)
Changed in psiphon: | |
milestone: | none → 2.4 |
milestone: | 2.4 → none |
milestone: | none → 2.4 |
visibility: | private → public |
Changed in psiphon: | |
status: | New → Fix Committed |
To post a comment you must log in.