|Frontier Tutorials / Writing an ObjectNotFoundHandler|
In a site served via Frontier's MainResponder dynamic website framework, you can do any or all of the above. You create a single entry called an objectNotFoundHandler; it can return any data you like in response to any URL within your website.
You've seen the default result of requesting an unknown URL from a MainResponder site:
Wouldn't you rather see:
By the end of this tutorial, you will be able to create an ObjectNotFound handler to return anything you want in response to a request for an unknown URL, including a more user-friendly Page-Not-Found page like the example above.
This tutorial is intended for experienced Frontier scripters. It requires familiarity with Frontier's UserTalk scripting language and with the MainResponder dynamic website framework.
Before continuing this tutorial, you should read and be familiar with the following mainResponder articles from Dr. Matt:
The Walk: How mainResponder resolves a requested URL and attempts to find the corresponding page.
Script Objects: How mainResponder serves script objects as website pages.
Redirection: How to do redirection in mainResponder--including avoiding common unexpected behavior.
|Keywords:||tutorial, mainResponder, 404, 404-NOT FOUND, objectNotFoundHandler|
|Level of Difficulty:||Moderate|