User Tools

Site Tools


custom_error_pages_for_your_site

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Last revision Both sides next revision
custom_error_pages_for_your_site [2022/02/13 22:25]
jquah
custom_error_pages_for_your_site [2022/02/13 22:33]
jquah
Line 44: Line 44:
  
 "ErrorDocument" indicates that you are defining your own, "404" is the error code you are taking responsibility for, and ''/404.html'' is the name and location of your custom error document. Please note that the "/" in front of the file name indicates that ''404.html'' may be found in the //www root directory of the site that the server is masquerading as// (a concept known as DOCUMENT_ROOT). Because the same physical computer might handle requests for multiple host names, the DOCUMENT_ROOT will be different for each SDF user's vanity domain. Whenever the original request makes use of a vanity domain, say, //altego.freeshell.org//, the custom error document in the html subdirectory of //altego//'s $HOME will be loaded with the syntax above. "ErrorDocument" indicates that you are defining your own, "404" is the error code you are taking responsibility for, and ''/404.html'' is the name and location of your custom error document. Please note that the "/" in front of the file name indicates that ''404.html'' may be found in the //www root directory of the site that the server is masquerading as// (a concept known as DOCUMENT_ROOT). Because the same physical computer might handle requests for multiple host names, the DOCUMENT_ROOT will be different for each SDF user's vanity domain. Whenever the original request makes use of a vanity domain, say, //altego.freeshell.org//, the custom error document in the html subdirectory of //altego//'s $HOME will be loaded with the syntax above.
 +
 +===== Changes needed if you use Apache's mod_userdir =====
  
 Some SDF users prefer to have their sites accessible via **tilde-style URLs**, like http://sdf.org/~altego . In this case the DOCUMENT_ROOT is no longer pointed at //altego//'s html directory, but instead to the root html directory for SDF as a whole. Hence the location of the custom error page must be modified like so: Some SDF users prefer to have their sites accessible via **tilde-style URLs**, like http://sdf.org/~altego . In this case the DOCUMENT_ROOT is no longer pointed at //altego//'s html directory, but instead to the root html directory for SDF as a whole. Hence the location of the custom error page must be modified like so:
Line 57: Line 59:
   - Upgrade your membership to MetaARPA and toggle vanity domain hosting to the MetaArray. The tilde-style URL will still resolve to the cluster, where ''ErrorDocument 404 /~altego/404.html'' will continue to work as before. The vanity domain will resolve to mab, where your content must be uploaded again into the appropriate directory, and the htaccess file modified to read ''ErrorDocument 404 /404.html''. With MetaARPA membership you can set up a cronjob to keep the contents of your two html directories (cluster and MetaArray) in sync.   - Upgrade your membership to MetaARPA and toggle vanity domain hosting to the MetaArray. The tilde-style URL will still resolve to the cluster, where ''ErrorDocument 404 /~altego/404.html'' will continue to work as before. The vanity domain will resolve to mab, where your content must be uploaded again into the appropriate directory, and the htaccess file modified to read ''ErrorDocument 404 /404.html''. With MetaARPA membership you can set up a cronjob to keep the contents of your two html directories (cluster and MetaArray) in sync.
  
-Of course, if you place the document in a subdirectory off your html root, you need to indicate that path in ".htaccess". If you are creating custom pages for additional codes, simply add the appropriate lines in ".htaccess".+===== Other changes you might need ===== 
 + 
 +If you place the document in a subdirectory off your html root, you need to indicate that path in ".htaccess". If you are creating custom pages for additional codes, simply add the appropriate lines in ".htaccess".
  
 After making your changes, it may be a good idea to reset the permissions on your website by entering the command: After making your changes, it may be a good idea to reset the permissions on your website by entering the command:
custom_error_pages_for_your_site.txt · Last modified: 2022/02/13 22:35 by jquah