• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

Resolved Custom error document - 414 - doesn't work

goobliata

New Pleskian
I've set up custom error documents, and am testing a few. They mostly work but for 414 - Request URI too long uses the default Apache document. I've tested this by going to <mydomain>/<1 million letters> using Chrome (some other browsers don't allow that many characters.)
 
Hello, can you provide an example how you configured custom error document (part of config file).
Can you confirm other error codes work as expected and you experience problem only with 414 error code?
 
Hello. I haven't edited any config files directly, I just ticked the checkbox under Hosting Settings (if you can tell me which config file I can check it.)

I've tested a few other error codes and they work as expected. I'm not sure how to trigger all of them, but the only one that I tested that failed was the 414.

Thanks!
 
Dear @goobliata
I confirm it's a bug in error document name, thanks for a report.
You can fix it manually (as a workaround) by open /var/www/vhosts/<your domain>/error_docs and copy file request-uri_too_long.html to request_uri_too_long.html
Copying will prevent failure when fix will be released.
 
Back
Top