Page MenuHomePhabricator

127.0.0.1, ::1, localhost, loopback, lo0 bugs (tracking)
Open, NormalPublic

Description

All bugs related to effects with 127.0.0.1 IP address being used for various automated tasks.


Version: 1.23.0
Severity: normal

Details

Reference
bz58272

Event Timeline

bzimport raised the priority of this task from to Normal.Nov 22 2014, 2:38 AM
bzimport set Reference to bz58272.
bzimport added a subscriber: Unknown Object (MLST).
saper created this task.Dec 10 2013, 1:57 PM
saper added a comment.Dec 10 2013, 2:18 PM

What about ::1? :)

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?

saper added a comment.Dec 10 2013, 3:24 PM

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.

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.

saper added a comment.Dec 10 2013, 7:25 PM

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.