if the document root directory is associated with group psacln instead of psaserv.
It could also be thinkable that only the index file is missing (by design), but other files could be addressed directly and the user does not want the requestor to know.Ī different case where a 403 is triggered is when access is indeed forbidden by permission, e.g. For example the web server could have the DirectoryIndex option set so that instead a directory listing could be displayed. This does not need to mean that access is prohibited.
htaccess file add code below to fileĤ03 would be "forbidden", but in the case of a missing index document, this is not a forbidden access, bus a missing index document. htaccess file add ErrorDocument 403 /403.html rule to fileĥ) Access domain via browser, notice how default apache welcome page is shown instead of custom error documentĤ) Create. However I would expect that a custom 403 error document to take precedence over the default apache welcome page as an error document.Ģ) Remove any index file from the document root of the domainģ) Create a custom error document for 403 error (403.html) in document rootĤ) Create. I am aware that showing the default apache welcome page when there is no index file present in the document root and directory listing is prohibited is (or used to be) common behavior for Apache. Just to be clear, this issue only relates custom error documents for 403 errors in the document root of a domain. In other scenarios that trigger a 403 error within the document root, for example when the SSLRequireSSL directive is used, a custom 403 error document isn't shown either. Instead the default apache welcome page is always shown (together with a 403 http response code of course). htaccess file or the Additional Apache directives it's never shown when there is no index file for the document root of a domain. When a custom 403 error document is configured for a domain trough either a. PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Custom 403 error document never shown for document root
0 kommentar(er)
