{"push_id":1297965770,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"ff537569e2a2f0ecaeecd11f17e4f6f981221f4e","before":"70f66028dd5fe16363cd65069414c5fe7d3727c1","commits":[{"sha":"ff537569e2a2f0ecaeecd11f17e4f6f981221f4e","author":{"name":"Paul Millar","email":"4a6a3bb8c9d01f48480af5e8f6480cef5e8e3747@desy.de"},"message":"webdav: fix Unauthorized vs Forbidden response\n\nMotivation:\n\nThe status code 401 Unauthorized indicates that there is an\nauthentication error; 403 Forbidden indicates there is a permissions\nproblem.  For more details, see:\n\n    http://www.dirv.me/blog/2011/07/18/understanding-403-forbidden\n\nWe may translate this to permission denied and Subject is NOBODY then\nreturn 401 (please try again, but with Authorization header), otherwise\nreturn 403 (please don't try again, instead someone to adjust\npermissions within dCache).\n\nCurrently WebDAV door return 401 on permission problems even when the\nuser is authenticated.  This results in clients prompting users to\nreauthenticate whenever the client makes a request that is denied for\nauthorisation reasons.\n\nModification:\n\nAdd helper method to return the correct exception; update code to make\nuse of this helper method.\n\nResult:\n\nClients can handle objects that they don't have permission to access.\n\nIt may be that some users were using that dCache returns the wrong\nstatus-code as a mechanism to clear the browser's BASIC credential cache\n(e.g., to \"log out\").  With this patch, that is not possible and users\nmust use the facilities the web-browser provides.\n\nTarget: master\nRequest: 2.16\nRequires-notes: yes\nRequires-book: no\nPatch: https://rb.dcache.org/r/9722/\nAcked-by: Gerd Behrmann","distinct":true,"url":"https://api.github.com/repos/dCache/dcache/commits/ff537569e2a2f0ecaeecd11f17e4f6f981221f4e"}]}
{"actor":{"display_login":"paulmillar"}}