The error-redirection processing for handling 404 can screw up the editing environment if we ever respond to an image request within a redirection to a full html page.

  1. When constructing a src= link for an image or av component, as within AgAnchorImmediate, we must not fall into common processing code where a /ittrium/visit reference will be built. This causes major problems with the browser.
  2. Likewise, we must not construct an empty reference since the browser can interpret this to mean a re-post of the current page. If no reference is available, then the scr= attribute must be left off.
  3. If a site is configured to use the reference servlet to supply images (rather than the /site construct) then in your error-redirect mapping, you must include a wildcard match of /ittrium/reference/* and post a 404 rather than a redirect.
  4. If you are defining a default redirect, be sure to map it through the /error servlet and never directly back into the site.

If 1, 2, 3, or 4 above is messed up, you can use Live HTTP Headers in Firefox to watch the bogus requests. What you will typically see is a request posted, looking for an image type, but with an inappropriate URL that results in a redirection. How the browser reacts is unpredictable, but typically unpleasant. A code fix for AgAnchorImmediate has been implemented, and basehtml.xsl handling of image references will not include the src= attribute if the given reference string is empty..