Dynamic custom error pages are a basic, essential feature of website hosting; it's how URL rewriting / friendly URLs work, and has been around for years. I was just migrated by GoDaddy to Plesk, which has much less functionality than the GoDaddy shared hosting I was on (WIndows Ultimate). A platform that drops server/script/session information every time a requested URL doesn't match a physical file ...? And just responds with a static page? You can't develop a customer experience with that. It will be a lot of work, but I will have to move this hosting away from GoDaddy

costume error page if you are using nginx

We have been hosting for many years with GoDaddy. Our recent upgrade of our sites to their newest platform failed and had to be rolled back, because they decided to use Plesk Panel which does NOT allow dynamic custom error pages -- which we ARE successfully using in GoDaddy's prior hosting platform (that does NOT use Plesk). Like Carsten and the others who left comments on the referenced link, a key element to the solutions we provide our clients requires the ability to read server, session, and subdomain information from the original error request and provide custom information back to the user. This server/session information is lost if the Plesk Full URL redirect option is used, and the original http/https & subdomain information is also lost if we are forced to specify a static Full URL in Plesk. Since Microsoft IIS allows this functionality, I believe it should be a minor effort to change the Plesk Panel to allow a custom dynamic error page like '/error404.asp' to be specified when 'File' is used in the 'Type' menu. And I think this may benefit others looking for the same custom error page functionality in Plesk Panel, as I found when searching GoDaddy's support site, and on the general Internet.