Globally, CharSet
not specified for the application.
This is actually more than just telling the client that it received UTF-8. You must also ensure that the response object is configured to code page 65001. This can at least be set globally using the AspCodePage
metabase AspCodePage
at the application level (or directly in the ASP function in IIS7 Manager).
However, my preference for this is to avoid a server freeze that will be configured correctly. Each page sets its own code page (either with the @CODEPAGE
directive, or with the help of Response.Codepage
) and its CharSet
.
I have two reasons for this approach. One of them is that ultimately CharSet / Codepage is the choice made during the creation and saving of the file. Another is that when you depolate / copy a site, the less you have to remember in order to configure it better.
source share