Returning 401 from a route - client vs server behavior
On some authenticated routes I return a 401 error via request middleware if the user doesn't have proper authorization. The behavior I see is:
* Server-rendered: properly receive 401.
* Client-rendered (eg via Router link): No indication of error at all.
I want to be able to control the message to the user when they hit a page they're not authorized to visit, regardless of whether the us gets there via server request or client load. Is there some better way to set this up - eg via a root beforeLoad?
* Server-rendered: properly receive 401.
* Client-rendered (eg via Router link): No indication of error at all.
I want to be able to control the message to the user when they hit a page they're not authorized to visit, regardless of whether the us gets there via server request or client load. Is there some better way to set this up - eg via a root beforeLoad?
