Forum Discussion
That would be an interesting customization. Just played around a bit and it seems (unfortunately) that the possibilities in that regard (customizing error pages) are very limited... I thought we might be able to catch an error code in the page init script with http.response.redirectStatus, but this just returns 0 if not explicitly set with http.response.setRedirectStatus(<int_http_status_code>) plus even if we set it we do not have a way to know if an error occured in the page init script because it's never reached once an error occurs. How do I know? I set an error code in the page init script, then provoked a 404 and the error code that is normally set via page init script is again 0, e.g. the init script is never processed in case of an error... keep us updated which rout you gonna take to customize this...
My idea was to redirect to a custom page once I would have determined the error code, but have to forget that idea again =)... maybe DougS knows some hidden stuff that could be used for that?
Related Content
- 7 years ago
- 9 years ago
- 2 years ago
- 3 years ago