Ha ha, yeah, its pretty important to understand how cflocation works if you are going to use it. In a similar scenario, I recently deployed a missing template handler, which uses cflocation to fall back onto a heirarchy of error handling pages without knowing what site it is in ( for a cf hosting company ), eventually falling back to the IIS 404 page. On the whole a really nice system :)
I spent a whole day beating my head against the wall because it wouldn't work, then I discovered that there is a check box in the cfide that allows cfmx to rewrite the header response on error pages so that cflocation doesn't work ( and its enabled by default ). Argh. Its right above the field for entering your error handler, with no indication that it will impact on your handler. Jon. --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MX Downunder AsiaPac DevCon - http://mxdu.com/
