Last modified: 2014-08-10 23:59:39 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T60258, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 58258 - MediaWiki doesn't warn about or disallow blocking localhost (127.0.0.1) which can cause weird bugs
MediaWiki doesn't warn about or disallow blocking localhost (127.0.0.1) which...
Status: NEW
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks: user-127.0.0.1
  Show dependency treegraph
 
Reported: 2013-12-10 06:27 UTC by MZMcBride
Modified: 2014-08-10 23:59 UTC (History)
8 users (show)

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


Attachments

Description MZMcBride 2013-12-10 06:27:19 UTC
MediaWiki doesn't warn about or disallow blocking localhost (127.0.0.1) which can cause weird bugs such as bug 58237. Perhaps it should do one or the other.
Comment 1 Marcin Cieślak 2013-12-10 14:16:58 UTC
I have opened bug 58237 for various issues related to 127.0.0.1 :)

I strongly believe (see e.g. https://gerrit.wikimedia.org/r/#/c/92050/ my comment to patchset 1) that 127.0.0.1 should be nothing special; 

1) if the operation is executed automagically on behalf of some realuser, her WebRequest should be taken (IP address, user agent, etc.) even if it's an automated action. That's why for example I think bug 42345 should be WONTFIXed as of now.

There is an edge case here what to do in case of delayed updates - they might appear as done from some IP address that can already be used by some other "person" later. Maybe IP address in the logs should always be separately timestamped irrelevant to the actual operation log?


2) otherwise we should have special means not to use real users at all in such scenario. I proposed various ways to solve this (https://gerrit.wikimedia.org/r/#/c/92252/, also some thoughts http://thread.gmane.org/gmane.science.linguistics.wikipedia.technical/73503).

In this particular case I think that MassMessage should be changed not to use 127.0.0.1
Comment 2 Marcin Cieślak 2013-12-10 14:17:47 UTC
bug 58272 is tracking "loopback" issues, not bug 58271.

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


Navigation
Links