php - using curl instead of fopen problems -

So, I've gone with trying to fix a PHP script on our Remote Access page. Basically it will use FOPN if any site is available. If it is a user, then it is directed to the site, if it was below, the next URL will be tested and the user will redirect it to success, etc.

The script should be composited for security reasons because of our new shared hosting site. I have tried my best to make some disturbances together, but I think that I am missing something, maybe quite original.

The script is the first index of three simple php files. PHP (it's running on Joomla, so I believe how it should be setup) and it looks like this:

URL.php is a list of only those 4 sites that are being tried in order. Functional PPP is the main thing and vegetarian, which I think and where I have tried my dub hand, in the curl instead of the cap in the hand:

   = 200 & amp; amp; amp; amp; amp; amp; amp; $ httpcode & lt; 300) is true; Second false return; If ($ httpcode == true) {header ('location:'. $ WebURL); Go out; } And {}}? & Gt;  

The last result of running this delay is zip if I click on the source on the correct page and load it, then the page "1, 2, 3" is going down. I am convinced that I have simplified some dead but my programming ability is just shy of nonsense and would be grateful to anyone looking at it. I think the curl stuff should be fine, but I wonder if I'm getting some distance link between index.php and workcript.php.

EDIT: After reading Belindas's suggestion below, I have changed the code to read it (I have only printed the lines that have changed which were all at the end of the script):

> if ($ httpcode> = 200 & amp; amp; amp; $ httpcode & lt; 300) {header ('location:'. $ WebURL); Go out; } And {}}? & Gt;

The code still falls, though weirdly it is mentioned before adding "4" "1, 2, 3" page is going down when you see the source . I can see it as only positive! Can anyone possibly get any type of gem because they can send me their way because I have to admit that I have this difficult test, although this is a pleasant test.

The statement of the header will not arrive because you are returning true or incorrect before reaching. Rather than returning the correct redirect to the httpcode between 200 and 300. Not sure it will solve it, but it should help.