Couldn’t see this implemented in any of your example applications on GitHub, nor in your documentation.
How do you set up custom error pages? I.e. when our users get 403 Forbidden, 404 Not Found or - God forbid - 500 Internal Server error - we’d like to provide them with a custom error page (preferably one for each).
ETA before tuesday… if nothing goes wrong.
You should be able to handle any http status code - naturally, only the onces that are actually produced by the system. Currently this is limited to 404, 401,403 and 500 (I believe)
When creating error pages, we recommend making them as simple as possible - simply to avoid errors on your error page - i.e. simply serve assets and static info, avoid requesting services etc…
@mla - your specific problem has been fixed - however, redirecting to a login page is not optimal (unless the errorpage is located in a remote app/site), rather just return a login form directly in the error response, this is optimal for http clients of any kind.