The HTTP API was written so that problems with fsockopen being disabled or fopen not working wouldn’t hinder fetching URI resources. It is also an attempt to replace Snoopy and standardize the internal HTTP requests.
There are currently five methods implemented for retrieving URI resources using the http or https (if available) protocols. The fsockopen is not used, except for the last fallback, if all of the others don’t work. The fopen() PHP function is used with two methods, one uses streams if PHP5+ is used and the other does not. That counts as two, in case you were not wondering or something. The other use the cURL and HTTP extensions, if they are available.
Basically, if you don’t have either the HTTP or cURL extensions installed and allow_url_fopen is disabled and fsockopen is part of disabled functions, then you are pretty screwed and WordPress can’t help you. You should probably try to find a better host.
Hopefully, the support questions about fsockopen being disabled and not being able to connect to the cron should go down. Well, that is when the HTTP API is stable in the next few months when it is fully tested and all of the minor issues are corrected.
Possibly Related Posts:
- Bullet: E-Book Library Management and Content Server
- Using ZendFramework 2 beta1 For Directory Project
- The Way of Kings and Cosmere Theory
- “In Time” Movie Premise Flawed
- Completing HTTP Library For PHP
Comments are closed.