Issue 54: Server Configuration Problem
Status:  Started
Owner: ----
Reported by mar...@havocdigital.com, Nov 22, 2011
Hi Sir Mewt 

I am using lightopenid on my localhost and it works fine but when I transferred it on my online dev-site it gave me multiple error messages

solution from the net says when i get those error message it is because my allow_url_fopen is disbled. but i tried disabling my localhost's allow_url_fopen and it still works fine..

i have curl enabled in my devsite and localhost..


this are the error messages:
http://dv10.havocdigital.com/ci203/


this is my devsite php_info: 
http://dv10.havocdigital.com/ci203/index.php/site/php_info

Please help me.. Thanks

Nov 23, 2011
Project Member #1 mewp...@gmail.com
Your problem on the server is caused not only by the fact that allow_url_fopen is disabled, but also because there's open_basedir.

When open_basedir or safe_mode are in effect, curl can't follow redirections, and therefore is disabled. And since allow_url_fopen is also disabled, php streams can't work either (and lightopenid should throw an exception in this case -- I'll change that).

In this case, LightOpenID (and any other OpenID library) simply can't work reliably.
I would advise to either change your hosting provider, or persuade it that allow_url_fopen should be enabled.

In theory, it probably is possible to work around that -- if not by following redirections manually, then by implementing a socket-based http client in php (there probably are libraries that do it). So if you really want to, you can try. However, an easier method would be to switch providers, if that's possible.
Status: Started
Nov 23, 2011
#2 mar...@havocdigital.com
Thanks Sir Mewp I'll try to work around it but if nothing works i'll probably request to enable allow_url_fopen Tnx tnx..
Nov 24, 2011
#3 mar...@havocdigital.com
just wondering sir mewp... are you going to release a version that uses a socket based http client.. tnx..
Nov 24, 2011
Project Member #4 mewp...@gmail.com
I have no plans to do so. It's a lot of code (probably more than the whole LightOpenID as of now) and would be of little use to most people.

Supporting both curl and streams requests already makes the library a lot bigger than it needs to be (in order to work on a good configuration).
Nov 24, 2011
#5 mar...@havocdigital.com
oh thanks  anyways...