Custom Error Pages
Find out what a Custom Error Page is, what function does it serve and the way to set up one.
If you have looked at lots of websites, you have probably encountered some error message now and again. An error may take place in case the web server cannot process a request (Error 400), if you need to log in so as to see some content and you haven't done so (Error 401), if you are not able to access some webpage (Error 403) or if a link leads to a file that isn't on the server (Error 404). Getting this kind of messages may sometimes be irritating because the pages have absolutely nothing in common with the actual Internet site. That’s why some hosting companies allow you to set your own error pages which will match the style of your own site and which can have any content which you want - info why the error has taken place, a suggestion how to handle it or even some witty remark. Such a feature will help you keep the visitor on the website no matter the error and the reason for it.
Custom Error Pages in Semi-dedicated Servers
Adding your personal pages for any of the four error types to any Internet site hosted through a semi-dedicated server
account with us will be really easy and shall not take more than a couple of mouse clicks. When you upload the files in your account, you can check out the Hosted Domains section of your Hepsia CP and edit each of the domains and subdomains listed there through an intuitive interface with drop-down navigation. You may select what page should display for every error type. Your choices are a standard Apache server page or a page from our system, and personalized pages. In case you select the aforementioned option, you need to enter the link to every page in your account, then save the change. The link or the sort of page that shows up in case a user encounters an error can be changed anytime. In case you are more experienced, you could use an .htaccess file to set in-house made error pages as well, as an alternative to using our integrated generator instrument, and if you pick this option, the file has to be positioned inside the root directory of a specific domain or subdomain.