[wp-trac] [WordPress Trac] #47057: Site Health: information about "loopback" connections is vague/misleading.

[WordPress Trac]

#47057: Site Health: information about "loopback" connections is vague/misleading.
----------------------------+------------------------------
 Reporter:  DavidAnderson   |       Owner:  (none)
     Type:  defect (bug)    |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Administration  |     Version:  trunk
 Severity:  normal          |  Resolution:
 Keywords:  site-health     |     Focuses:
----------------------------+------------------------------

Comment (by DavidAnderson):

 "the most prominent ones" - are there any others in WP core at all? I
 can't think of any. If there's a separate cron check, then for 99.9% + of
 users, they're being untroubled unnecessarily. Rather than tweaking the
 wording, I'd suggesting having this check off by default, and providing a
 filter so that plugins that need loopback to work can turn the check back
 on. Then "features relying on them are not currently working as expected"
 would be known to actually mean "actual features" rather than "features
 you're not using". As-is, it's most useful function would be to strong-arm
 hosting companies to not prevent loopback. If that's the intended purpose,
 I wouldn't personally object. But if that's not the intended purpose, then
 I don't think it currently really has one.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/47057#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform