Posts: 4
Threads: 4
Joined: May 2008
While i am trying to update the answers i get the following message
Warning: file_get_contents(
http://answers.yahooapis.com/AnswersServ...results=50) [function.file-get-contents]: failed to open stream: HTTP request failed! HTTP/1.1 408 Request Timeout in /home/oustas/public_html/includes/domain.php on line 570
Why is that happening?
Andreas
Posts: 89
Threads: 13
Joined: Nov 2007
This could be happening due to a slow down at Yahoo! If you get this error, you may want to simply give it another try in a few minutes. This error is a result of a slow response from Yahoo!, so there is not much that can be done within the software itself to correct these occurrences.
Posts: 18
Threads: 4
Joined: Nov 2007
This is the error I have been experiencing for some weeks now, You mentioned the 5000 API Calls but it just seems odd since I have maybe 40-50 sites max on 1 IP and its only been happening over the last couple of weeks so I take it that it might be a glitch on yahoos side, but how long do we wait and whats the next steps...
thanks
Posts: 5
Threads: 1
Joined: Jul 2008
I have 2 sites and I am experiencing this issue.
Posts: 5
Threads: 0
Joined: Jul 2008
tradedemon Wrote:This is the error I have been experiencing for some weeks now, You mentioned the 5000 API Calls but it just seems odd since I have maybe 40-50 sites max on 1 IP and its only been happening over the last couple of weeks so I take it that it might be a glitch on yahoos side, but how long do we wait and whats the next steps...
Are you still experiencing this error?
yoyo Wrote:I have 2 sites and I am experiencing this issue.
Does it happen with all keywords?
Did you obtain your own Yahoo Application ID? If not, you can get one here:
http://search.yahooapis.com/webservices/...pplication
If you do have an ID, try replacing it temporarily with
YahooDemo in the Kwikcontent setup and check if the error still occurs.
Posts: 18
Threads: 4
Joined: Nov 2007
Had to make some tweaks to the code to fix this.
thanks
Posts: 5
Threads: 1
Joined: Jul 2008
It is 100% an IP thing.
My very helpful host moved my sites for me and I was able to continue to set up sites until the error occured again, he then moved the sites again and again I was OK for a while.
Janie