If you're getting a CAPTCHA back in response to that type of API
request (as opposed to a ClientLogin authentication request) then my
hunch is that it's generated not by the YouTube API servers but
instead by the generic Google web infrastructure that sits in front of
our YouTube API servers and handles HTTP traffic. I don't have any
details to share about what specifically could trigger our HTTP
infrastructure to start returning CAPTCHAs or other types of error
responses—something about your HTTP traffic might have been deemed
suspicious.
If you visit www.google.com on a web browser from the same machine
that you're seeing failed API requests from, do you get back the same
sort of CAPTCHA response?
Cheers,
-Jeff Posnick, YouTube API Team
groups.google.com/group/youtube-api-gdata | apiblog.youtube.com |
@YouTubeDev
On Jan 10, 7:23 pm, toy <noppani...@gmail.com> wrote:
> I got error while making a request to this urlhttps://gdata.youtube.com/feeds/api/videos/*videoid*?v=2
>
> to get information about that youtube video, and it returns the CAPTCHA.
> BTW I'm requesting to http:// not https://. Not sure if that's the case?
--
You received this message because you are subscribed to the Google Groups "YouTube APIs Developer Forum" group.
To post to this group, send email to youtube-api-gdata@googlegroups.com.
To unsubscribe from this group, send email to youtube-api-gdata+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/youtube-api-gdata?hl=en.
No comments:
Post a Comment