Avoid relays resolving their own address on every download status check

My branch 21789-mitigate has a fix that avoids relays doing useless resolves every time they check a download status. (And clients never do those resolves, because they're clients.)

changed milestone to %Tor: 0.2.9.x-final

added 028-backport-maybe-not 029-backport 030-backport 031-backport actualpoints::0.2 component::core tor/tor milestone::Tor: 0.2.9.x-final parent::21789 points::0.2 priority::medium resolution::fixed severity::normal status::closed type::defect version::tor 0.2.8.1-alpha labels

Trac:
Status: new to needs_review

This looks fine to me. Should we consider backporting this?

Trac:
Status: needs_review to merge_ready

It needs a minor fix to the changes file and commit message to add this bug number, because trac was down.

Trac:
Status: merge_ready to needs_revision

See my branch bug23470, it has the same code, but the commit message and changes file use this bug number.

Trac:
Status: needs_revision to merge_ready

And now bug23470-029.

Trac:
Keywords: N/A deleted, 030-backport, 028-backport-maybe-not, 029-backport, 031-backport added

Trying this in master, marking for possible backport.

Trac:
Milestone: Tor: 0.3.2.x-final to Tor: 0.3.1.x-final

Seems to have worked out okay since 0.3.2.1-alpha; backporting to 0.2.9 and forward.

Trac:
Milestone: Tor: 0.3.1.x-final to Tor: 0.2.9.x-final
Resolution: N/A to fixed
Status: merge_ready to closed

closed

changed time estimate to 1h 36m

added 1h 36m of time spent

moved to tpo/core/tor#23470 (closed)