[wp-trac] [WordPress Trac] #60934: Internal Subnets are being blocked by wp_parse_url and why?

[WordPress Trac]

#60934: Internal Subnets are being blocked by wp_parse_url and why?
-------------------------------------+------------------------------
 Reporter:  erenfro                  |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  Awaiting Review
Component:  HTTP API                 |     Version:  trunk
 Severity:  normal                   |  Resolution:
 Keywords:  close reporter-feedback  |     Focuses:
-------------------------------------+------------------------------

Comment (by erenfro):

 Okay. In think then in the case of this report, at the very least, this
 needs to be documented better, and possibly even reasonable examples of
 _how_ to work with this, because the way people are doing it ends up
 actually often times being worse. Or maybe even a whitelist rules editor
 added into WordPress to be able to configure this, rather than it being
 basically a black hole solution that literally nobody, but wordpress
 developers, and some plugin developers, even know about. I went through
 various WordPress communities over this issue. IRC, Discord, non-specific
 communities that weren't specific to wordpress but were involved in social
 communities and the likes, but literally nobody know about this, and to
 me, that's a problem. It solves a problem, sure, but without ever
 providing a clear understanding of it.

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