[wp-hackers] stop HTTP requests made behind one's back
wordpress at santosj.name
Wed Feb 18 04:41:16 GMT 2009
Yeah, you know, I could have spent another week or two implementing
proxy support, but I'm just like, "You know, those people probably
amount to only a small fraction of the users, so why should I waste my
time?" That and the fact that I don't tend to cut myself, unless I've
done something socially awkward. From the complaining of other
developers about the pain and suffering of implementing proxy support,
I'll keep away from it.
That said, there is nothing preventing you (either of you or anyone else
with ability to do so) from creating a patch that adds proper proxy
support. If you do it well enough, I might send you a gift (disclaimer:
I'm not going to send you a gift) and you'll have my gratitude (that is
free and has not monetary redeemable value).
It serves no purpose for me, which is the most important reason why I
didn't implement it nor will I implement it in the future. I do not host
WordPress behind a proxy, therefore well, it would be impossible for me
to develop a solution anyway, because I would fail to be able to test
whether or not it works (for that proxy and version).
So I mean, those fraction of users whose host has screwed them will
appreciate it. There there are you two.
Doug Stewart wrote:
> On Tue, Feb 17, 2009 at 8:34 PM, <jidanni at jidanni.org> wrote:
>> HOW ODD, I said to myself, WordPress seems to make a lot of outbound
>> HTTP requests, from the minute you first install it.
>> Why can't there at least be a checkbox provided to make WordPress act
>> like MediaWiki: just respond to incoming HTTP requests.
>> An RSS reader bundled right into the Dashboard? How kind, but I have
>> my own. OK, I disabled it along with pings, etc.
>> cron update_core, update_plugins, update_themes? Again how thoughtful,
>> however there should be a way to not trust, and turn off such "beacons".
>> How is one to install WordPress on a military or intranet where making
>> HTTP requests to the Internet is not allowed?
>> Just rip up wp-includes/http.php? That won't stop other parts of the
>> code from then futilely hammering it even more.
> How serendipitous. I've been working on a BTF (Behind the Firewall) plugin
> for my clients for exactly the same reason -- the admin panel is SLOOOOOOOOW
> for both WP and WPMU when a firewall/proxy sits between it and the Internet.
> This opens this topic to the whole wp-hackers list though, and I'd love an
> How can we get wp-includes/http.php to respect a proxy? Used to be able to
> do it by editing the Snoopy files, but since the new http interface came
> in, it's nigh-impossible.
More information about the wp-hackers