The Jamba CMS is extensively tested for defects but inevitably (as with any website) there will be times when a page of your site cannot be displayed.

For example, a visitor may type the address of your page into the browser address bar incorrectly. If the CMS cannot find the page they are looking for, a friendly 'page not found' message is displayed. Similarly, if a visitor attempts to access a page with a status of anything other than 'public', an appropriate message is displayed.

In the unlikely event that an error occurs within the CMS itself, the details of the problem are automatically emailed to us so we can investigate the problem at the earliest opportunity.

HTTP response headers

Aside from a friendly message for the visitor, the CMS will also return relevant HTTP response headers to ensure that search engine spiders index your website pages correctly:

• Page not found (i.e. a broken link) - response code 404
• Unauthorised (i.e. page not public) - response code 401
• Gone (i.e. page archived) - response code 410
• Error (i.e. an unexpected server error) - response code 500
• OK (i.e. page found)