• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Question Nginx not use charset UTF-8 for xml...?

Azurel

Silver Pleskian
Server operating system version
AlmaLinux 8.8 (Sapphire Caracal)
Plesk version and microupdate number
Plesk Obsidian Version 18.0.53 Update #2
I verified a XML file with w3.org and get back:
This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.
Your feed appears to be encoded as "UTF-8", but your server is reporting "US-ASCII"

XML files are served by nginx and not in utf-8? What with Javascript? How I can change that in plesk?
 
That's something you define in your XML file. Like:

XML:
<?xml version = "1.0" encoding = "UTF-8" standalone = "no" ?>
 
This is what the line says. In the file utf8 is specified (with encoding="UTF-8"), but the XML-file is sent as charset US-ASCII.
 
Content-Encoding: br
Content-Type: text/xml
Date: Wed, 19 Jul 2023 08:24:21 GMT
Etag: W/"64b6f061-6009"
Last-Modified: Tue, 18 Jul 2023 20:04:49 GMT
Server: nginx
Vary: Accept-Encoding

another servers response here with
Content-Type: application/xml; charset=UTF-8
 
So, you need to fix the Content-Type header. You can use something like AddCharset UTF-8 .xml in Apache config (e.g. in .htaccess) if you have Apache behind nginx or charset utf-8; in nginx configs.
 
Not all documents in the world are in UTF-8, so forcing that on web server level by default is risky.
 
Back
Top