> -----Original Message----- > From: ioannes@xxxxxxxxxxxxxx [mailto:ioannes@xxxxxxxxxxxxxx] > Sent: Sunday, April 25, 2010 10:44 PM > To: ash@xxxxxxxxxxxxxxxxxxxx; tommyhp2@xxxxxxxxx >> Tommy Pham > Subject: Re: CURL cannot connect to URL - IP address - after successful > connection > > The answer I got from support desk on my shared server: 'You are trying to > curl to a datapipe server, if it is rejecting the server name and port, you will > need to take that up with them.' > > John I assume that you did full testing with the browser as I suggested? If everything works, one other thing to keep in mind is that the target also may implement reverse DNS lookup in their anti-bot. One good way to test that is to remote in via SSH (if on Linux/Unix) to test with wget. Otherwise, I'm pretty sure that target site have some anti-bot mechanisms in place. Microseconds of analyzing valid 'user' requests is better than processing 2-3 seconds and sending the response which will consume bandwidth. What you could also try is setting different user-agents for every request and use cookies in cURL should the target site have an anti-bot mechanism. Regards, Tommy -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
