All bugs related to effects with 127.0.0.1 IP address being used for various automated tasks.
Version: 1.23.0
Severity: normal
Description
Description
Details
Details
- Reference
- bz58272
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T60272 127.0.0.1, ::1, localhost, loopback, lo0 bugs (tracking) | |||
| Resolved | Dreamy_Jazz | T39971 No results on CheckUser query from 127.0.0.1 on PostgreSQL | |||
| Resolved | None | T36838 127.0.0.1 in CheckUser log: Editing APIs should never use FauxRequest | |||
| Resolved | RyanLane | T45603 Edits as 127.0.0.1 | |||
| Resolved | Dreamy_Jazz | T44345 Blocks from AbuseFilter show up as performed from the target's IP address in Checkuser | |||
| Resolved | Dreamy_Jazz | T311340 Allow the CheckUser extension to store an IP other than the IP from the request | |||
| Declined | None | T59815 Some AbuseFilter entries on Wikidata wrongly attributed to localhost | |||
| Resolved | None | T60237 MassMessage is being affected by autoblocks on 127.0.0.1 | |||
| Resolved | Nikerabbit | T70234 TranslateDeleteJob makes edits as 127.0.0.1 | |||
| Open | None | T60258 MediaWiki doesn't warn about or disallow blocking localhost (127.0.0.1) which can cause weird bugs | |||
| Resolved | None | T69504 Recent changes attributes certain uploads on Commons to 127.0.0.1 |
Event Timeline
Comment Actions
Thanks for filing this. I had a similar thought about creating such a tracking bug as I filed bug 58258.
(In reply to comment #1)
What about ::1? :)
The bug summary should probably include the word "localhost", no?
Comment Actions
Hm.. just a thought... we are just about to remove rc_cur_time from recentchanges (bug 40667).. what about re-using this field for providing timestamp of rc_ip?
For delayed jobs we would have an actual change timestamp (rc_timestamp) and "IP address timestamp" (rc_cur_time, maybe renamed)...
Similar timestamp would have to be added in other tables like logging or checkuser.
Just an idea.
Comment Actions
What does the "timestamp of rc_ip" mean? My understanding is nothing should be marked with 127.0.0.1/localhost as the editor (when this happens, it's a bug), regardless of whether it's delayed.
Comment Actions
That would be ideal not to have 127.0.0.1.
I'd say something like this:
IP A.B.C.D issues request on Tue Dec 10 19:23:50 UTC 2013.
This request has some delayed/callback/whatever processing
that gets executed two minutes later, Tue Dec 10 19:25:50 UTC 2013.
This request gets logged with
rc_timestamp 201312101925
rc_ip A.B.C.D
rc_cur_time 201312101923 - the time when the request from A.B.C.D was taken.