Spletno mesto bo delovalo z omejenimi zmožnostmi, medtem ko na njem izvajamo vzdrževalna dela za vas. Če članki ne rešijo vaše težave in želite zastaviti vprašanje, naša skupnost za podporo čaka na vas na @FirefoxSupport na Twitterju in na /r/firefox na Redditu.

Avatar for Username

Iskanje po podpori

Izogibajte se prevarantski tehnični podpori. Nikoli vam ne bomo naročili, da pokličete telefonsko številko ali nam pošljete osebne podatke. Sumljivo dejavnost prijavite z gumbom »Prijavi zlorabo«.

Več o tem

Ta tema je arhivirana. Postavite prosim novo vprašanje, če potrebujete pomoč.

HTML page content type has charset=iso-8859-1 but document.characterSet is 'UTF-8'

gilles.poirot
gilles.poirot
more options

Hi,

I'm a web developer and I have an issue document.characterSet property from DOM API has an incorrect value on a non UTF-8 page

Firefox version: 95.0.2

1. HTML page is returned with following content-type content-type: text/html; charset=iso-8859-1

2. JavaScript code in the page reads document.characterSet property

Expected characterSet value is "ISO-8859-1"

Actual characterSet value is "UTF-8"

Thanks and regards,

Hi, I'm a web developer and I have an issue document.characterSet property from DOM API has an incorrect value on a non UTF-8 page Firefox version: 95.0.2 1. HTML page is returned with following content-type content-type: text/html; charset=iso-8859-1 2. JavaScript code in the page reads document.characterSet property Expected characterSet value is "ISO-8859-1" Actual characterSet value is "UTF-8" Thanks and regards,

Vsi odgovori (2)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

What encoding does the server send ?

If the server sends encoding "UTF-8" then that prevails and Firefox ignores a possible specification in the actual file for security reasons.

gilles.poirot
gilles.poirot Lastnik vprašanja
more options

I observed this behavior while working on a customer incident. The server responds with a content-type header which is "text/html; charset=iso-8859-1"

I tried to reproduce on a sample but in my test, I get the expected "window-1252".

However, if the response body contains an UTF-8 BOM, content-type header is ignored and document characterSet is "UTF-8"

Here is a small sample https://glitch.com/edit/#!/document-charset

Is this the intended behavior?