• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Question Verbs allowed by default in PHP

Duarte N

New Pleskian
Server operating system version
Windows Server 2022
Plesk version and microupdate number
Plesk Obsidian v18.0.55
Hi!

We have noticed that some Wordpress sites have JSON errors because the php handler (created by Plesk) does not allow the "OPTIONS" verb (in IIS handlers mappings).

Verbs are defined in handler mappings at the website level created by Plesk.
In other words, we cannot define them in the root of IIS so that they can be inherited by websites, as in the SolidCP control panel for example.

Somewhere in Plesk, it has definitions of the verbs that are allowed when the website is created, because there is nothing that can be inherited from IIS:
IIS does not have any PHP configuration in the root.
The "PHP-php" handler for the "*.php" file only exists on the website created by Plesk.

Does anyone know how I can get the verb "OPTIONS", in addition to the verbs "GET,HEAD,POST", to be allowed when creating the website?
 
This is important because around 40% of websites on the Internet are Wordpress and an anomaly occurs in IIS that causes the error: "The response is not a valid JSON response".

This article addresses one of the scenarios in which this happens:

In shared hosting, the ideal is to activate this function by default when creating the website, to avoid unnecessary support requests.
 
Back
Top