[wp-hackers] Heads-up for people debugging fopen/etc. issues
internally on PowWeb...
davebytes at comcast.net
Tue Oct 18 21:16:07 GMT 2005
Since I just ran into this, though others in the developer community might
find this info useful.
PowWeb, in their infinite wisdom, has implemented some kind of
load-balancing solution for their websites. This has the side effect of
basically locking-up any internal fopen/etc. request from a powweb page FOR
a powweb page, using 'normal' URL conventions.
The solution (spent 10 minutes in the powweb forums looking at PHP Q&A) is
to rewrite internal requests to use 'localhost'.
So if you want to reference:
... internally from powweb and somesite is on powweb, it must be rewritten
... when trying to fopen/fsockopen/etc. that page. I'm not altogether sure
if it is only the case if trying to fopen a somesite.com page FROM
somesite.com code (i.e. a site trying to fopen URLs to itself...), or if
it's a PowWeb-wide issue (i.e., a powweb site fopening a URL to another
Since it was causing an issue for a guy trying to aggregate his own feed
(using my CG-FeedRead plugin), I just figured others might want to know.
Don't know if it's useful enough to want to go into the Wiki or not. ;)
More information about the wp-hackers