https://www.redmine.org/
https://www.redmine.org/favicon.ico?1679302129
2017-08-14T13:42:06Z
Redmine
Redmine - Feature #26677: HTTP code 401 on login failure
https://www.redmine.org/issues/26677?journal_id=80618
2017-08-14T13:42:06Z
Holger Just
<ul></ul><p>The 401 status code is specifically used for Basic or Digest authentication. It has no value when using form authentication as done with Redmine.</p>
<p>If Redmine would return a 401 here, your browser would ask for authentication with a Basic-Auth form, similar to</p>
<p><img src="https://i.stack.imgur.com/5C6Pp.png" alt="" /></p>
<p>This not what we want. As such, returning a 200 is okay here for the user. When querying the API, we do already return a 401 if the user did not provide any credentials along with their request. API clients are equipped to deal with this.</p>
Redmine - Feature #26677: HTTP code 401 on login failure
https://www.redmine.org/issues/26677?journal_id=80622
2017-08-14T13:52:11Z
RĂ©mi Saurel
<ul></ul><p>This is not what I obtain with other services (e.g. with Jenkins CI instances), where a 401 code is returned, and presents the usual HTML login form (not through the browser, as the authentication is made through the application, not the web server).</p>
Redmine - Feature #26677: HTTP code 401 on login failure
https://www.redmine.org/issues/26677?journal_id=112386
2024-01-21T17:00:11Z
Go MAEDA
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Closed</i></li><li><strong>Resolution</strong> set to <i>Wont fix</i></li></ul>