I think this is what happened. As the application was trying to open our url domain the request was sent to the load balancer, and as it does not accept internal requests, the connection was timed out. The only way we could avoid that is to not use fopen our url, is that right? On Mon, Feb 11, 2013 at 4:26 AM, marco@xxxxxxxxxx <marco@xxxxxxxxxx> wrote: > > > Adam Tong <adam.tongu@xxxxxxxxx> hat am 10. Februar 2013 um 23:41 geschrieben: >> Hi, >> >> We had an issue with the code of a junior php developer that used >> fopen to load images using the url of the companies website that is >> load balanced. >> >> We could not the detect the problem in dev and test because the dev >> and test servers are not load balanced. >> >> I know that he could load the images using just the filesystem, but I >> am curious to know why it failed and if the load balancer is really >> the source of the problem or it is a limitation on the function >> itself. > > Do you have any error messages for us? > If the load balancer accessable from the internal servers? Normally it is not. > > >> >> Thank you >> >> -- >> PHP General Mailing List (http://www.php.net/) >> To unsubscribe, visit: http://www.php.net/unsub.php >> > > -- > Marco Behnke > Dipl. Informatiker (FH), SAE Audio Engineer Diploma > Zend Certified Engineer PHP 5.3 > > Tel.: 0174 / 9722336 > e-Mail: marco@xxxxxxxxxx > > Softwaretechnik Behnke > Heinrich-Heine-Str. 7D > 21218 Seevetal > > http://www.behnke.biz > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
