> What I do in this situation is simply direct the output to a custom 404-style > error page in fbx_layouts. > > The problem is that this gets returned with a status code of 200 (because > Active4D didn't detect any problem) and when I call set response status(404) > then Active4D delivers it's own 404 page, not the custom one.
You can thank Microsoft for this. IE6 refused to show a custom error page with a status code other than 200. Now that IE6 is irrelevant, I'll see if IE7+ behaves correctly, and if so I'll allow status codes other than 200. Regards, Aparajita _______________________________________________ Active4D-dev mailing list [email protected] http://list.aparajitaworld.com/listinfo/active4d-dev Archives: http://vasudev.aparajitaworld.com/archive/active4d-dev/
