MediaWiki doesn't warn about or disallow blocking localhost (127.0.0.1) which can cause weird bugs such as T60237. Perhaps it should do one or the other.
See Also:
Description
Description
Details
Details
- Reference
- bz58258
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T60272 127.0.0.1, ::1, localhost, loopback, lo0 bugs (tracking) | |||
| Open | None | T60258 MediaWiki doesn't warn about or disallow blocking localhost (127.0.0.1) which can cause weird bugs |
Event Timeline
Comment Actions
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;
- 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?
- 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