nmdpa3 Posted May 23 Share Posted May 23 (edited) Will this be an issue with WHMCS Plesk modules? For anyone who's using the Plesk REST API, please note that starting from Plesk Obsidian 18.0.62, requests to REST API containing the Content-Type header with a media-type directive other than “application/json” will result in the HTTP “415 Unsupported Media Type” client error response code. Since the curl commands send the “Content-Type: application/x-www-form-urlencoded” header by default, you need to add the --header "Content-Type: application/json" option to such commands to keep them working correctly. We strongly recommend that you check your existing integrations that use cURL for compliance with this change and update them if necessary. Failure to do so may result in any such integrations ceasing to work after updating to Plesk Obsidian 18.0.62. Edited May 23 by nmdpa3 0 Quote Link to comment Share on other sites More sharing options...
nmdpa3 Posted May 28 Author Share Posted May 28 (edited) So, WHMCS doesn't know or doesn't want to comment at this point, or does not reply in their community forums? We're also opening a ticket with same request. Plesk is currently at 18.0.61 Update #4, so 18.0.62 has to be right around the corner. This is critical to know. Edited May 28 by nmdpa3 0 Quote Link to comment Share on other sites More sharing options...
WHMCS Technical Analyst II Solution WHMCS Stephen Posted May 29 WHMCS Technical Analyst II Solution Share Posted May 29 Hello, Our WHMCS Plesk server module integration will not be immediately impacted by this change. The module does support the latest version of Plesk as such nothing is required on your side with WHMCS and our provisioning module. I hope this information helps. 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.