I just noticed that there is a warning message pops up when I view my mootool.js script on FireFox browser.
The warning message is "The character encoding of the plain text document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the file needs to be declared in the transfer protocol or file needs to use a byte order mark as an encoding signature.
does that mean I have to add a Charset or something? but it is a script!!
Is there a solution for this?
For HTML5:
Simply add to your
<head>
I got this error using Spring Boot (in Mozilla),
because I was just testing some basic controller -> service -> repository communication by directly returning some entities from the database to the browser (as JSON).
I forgot to put data in the database, so my method wasn't returning anything... and I got this error.
Now that I put some data in my db, it works fine (the error is removed). :D
In your HTML it is a good pratice to provide the encoding like using the following meta like this for example:
But your warning that you see may be trigged by one of multiple files. it might not be your HTML document. It might be something in a javascript file or css file. if you page is made of up multiples php files included together it may be only 1 of those files.
I dont think this error has anything to do with mootools. you see this message in your firefox console window. not mootools script.
maybe you simply need to re-save your html pages using a code editor that lets you specify the correct character encoding.
If you are using ASP.NET Core MVC project. This error message can be shown then you have the correct
cshtml
file in yourViews
folder but the action is missing in your controller.Adding the missing action to the controller will fix it.
Check your URL's protocol.
You will also see this error if you host an encrypted page (https) and open it as plain text (http) in Firefox.
FireFox is reporting that the response did not even specify the character encoding in the header, eg.
Content-Type: text/html; charset=utf-8
and not justContent-Type: text/plain;
.What web server are you using? Are you sure you are not requesting a non-existing page (404) that responds poorly?