On 06/02/2012 01:49, terry.rank...@csiro.au wrote:
When a user logs out, closes the browser, and then reopens it (clean
start) and loads a bookmark of a project URL which is valid, he gets a
404 (not found) instead of a 401 (not authorised).
I don’t think that this is really the right behaviour, I would suggest
using the 401, or redirecting it to the top level login.
AFAIK, this is a security feature -- i.e. by returning 404 no
information is leaked to unauthorised users about the existence or
non-existence of any given job.
But in any case, a nicer-looking error page could be good -- though I'm
not sure whether Jenkins can directly solve this given that the
underlying web server is presumably the one handling the 404s.
Regards,
Chris
