|
Hello Diego, I suppose you are running with Restlet 1.0, since Restlet 1.1 behaves differently (returns 401 status). We think that this behaviour won't be changed in the future. Thus, we kindly encourage you to use Restlet 1.1 or create a subclass and override the "forbid" method (which sets the 403 status). Best regards, Thierry Boileau -- Restlet ~ Core developer ~ http://www.restlet.org Noelios Technologies ~ Co-founder ~ http://www.noelios.com Hello, By default Guard returns 403 (forbidden) if authentication fails? Shouldn't it be 401?401: The request requires user authentication 403: request, but is refusing to fulfill it as it could be explained in the entity. br, DIego |
- Guard, authenticate failure, HTTP 401 Diego Ballve
- Re: Guard, authenticate failure, HTTP 401 Thierry Boileau
- Re: Guard, authenticate failure, HTTP 401 Diego Ballve
- Re: Guard, authenticate failure, HTTP 401 Thierry Boileau
- Re: Guard, authenticate failure, HTTP 401 Diego Ballve
- Re: Guard, authenticate failure, HTT... Thierry Boileau
- Re: Guard, authenticate failure,... Diego Ballve
- Re: Guard, authenticate failure, HTTP 401 Stephan Koops

