Last modified: 2007-08-09 09:54:07 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 10298 - wrong wait time returned after failed login
wrong wait time returned after failed login
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
API (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Yuri Astrakhan
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-06-17 21:44 UTC by Stefan Bauer
Modified: 2007-08-09 09:54 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Stefan Bauer 2007-06-17 21:44:12 UTC
I just tested a API login script and noticed the following behavior:

If username/password are ok, then everything is fine.

If an error occurs a wait=10 is returned (always the same time - wait = 10 seconds?), but if using this wait time with sleep I still get the same error message (password is ok) - if I wait longer (tested with 2 minutes) everything is fine again.

I assume therefore a wrong wait time is returned.

Furthermore I would propose a new result message if an attempt is started without waiting long enough - something like "WaittimeToShort" - would be helpful since in most cases a human person enters the password and tries to figure out if something got wrong.
Comment 1 Yuri Astrakhan 2007-08-09 09:54:07 UTC
Fixed in r24695

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links