0

accessing mybloglog member

Okay,
yahoo says on this page
http://developer.yahoo.com/yql/guide/select-chapt.html
that to access public data without the need for authorization and is wide open I use YQL URL's of this format
http://query.yahooapis.com/v1/public/yql?q=[command]
now on this page
http://developer.yahoo.com/yql/guide/data-sets.html
yahoo says that data sets with an asterix next to them are available using the public URL for YQL. The mybloglog data set is
mybloglog

* mybloglog.community.find*
* mybloglog.member *
* mybloglog.member.contacts *
* mybloglog.member.newwithcontacts *
* mybloglog.member.newwithme *
* mybloglog.members.find *
* mybloglog.stats.find

This clearly states that mybloglog.member is a publicly available aspect of the mybloglog data set which I should be able to access without authorization, in a totally free environment
When I go to the yahoo query language console
http://developer.yahoo.com/yql/console/
I click the mybloglog data table in the lower right panel and then click the mybloglog member button. This REST Query comes up
http://query.yahooapis.com/v1/public/yql?q=select%20*%20from%20mybloglog.member%20where%20member_id%20in%20(select%20id%20from%20mybloglog.members.find%20where%20guid%3Dme)&format=xml
And, in the formatted view the information is displayed. But, when I post the REST URL into the browser address, this comes as the XML
<error yahoo:lang="en-US">

<diagnostics>
<publiclyCallable>true</publiclyCallable>
</diagnostics>

<description>
Cannot authenticate user to fetch value of 'me'. You need to be logged in for this query
</description>
</error>

<!--
yqlengine1.pipes.re4.yahoo.com uncompressed/chunked Wed Mar 18 18:01:04 PDT 2009
-->

Now, i don't understand how it is publicly callable yet authentification is needed?
Is this a bug, or what. Please Help me. From yahoo's own stated logic, this should not happen.

2 Replies
  • The nested query is the one which needs the authentication - if you'll try the query
    select * from mybloglog.member where member_id = 2008110507453882
    you'll see that it works!

    BTW - this is my MyBlogLogID...

    Good Luck!

    QUOTE (Monsignor K. Kuwajukaba @ Mar 18 2009, 05:02 PM) <{POST_SNAPBACK}>
    Okay,
    yahoo says on this page
    [color="#FF0000"]http://developer.yahoo.com/yql/guide/select-chapt.html
    that to access public data without the need for authorization and is wide open I use YQL URL's of this format
    http://query.yahooapis.com/v1/public/yql?q=[command]
    now on this page
    http://developer.yahoo.com/yql/guide/data-sets.html
    yahoo says that data sets with an asterix next to them are available using the public URL for YQL. The mybloglog data set is
    mybloglog

    * mybloglog.community.find*
    * mybloglog.member *
    * mybloglog.member.contacts *
    * mybloglog.member.newwithcontacts *
    * mybloglog.member.newwithme *
    * mybloglog.members.find *
    * mybloglog.stats.find

    This clearly states that mybloglog.member is a publicly available aspect of the mybloglog data set which I should be able to access without authorization, in a totally free environment
    When I go to the yahoo query language console
    http://developer.yahoo.com/yql/console/
    I click the mybloglog data table in the lower right panel and then click the mybloglog member button. This REST Query comes up
    http://query.yahooapis.com/v1/public/yql?q=select%20*%20from%20mybloglog.member%20where%20member_id%20in%20(select%20id%20from%20mybloglog.members.find%20where%20guid%3Dme)&format=xml
    And, in the formatted view the information is displayed. But, when I post the REST URL into the browser address, this comes as the XML
    <error yahoo:lang="en-US">

    <diagnostics>
    <publiclyCallable>true</publiclyCallable>
    </diagnostics>

    <description>
    Cannot authenticate user to fetch value of 'me'. You need to be logged in for this query
    </description>
    </error>

    <!--
    yqlengine1.pipes.re4.yahoo.com uncompressed/chunked Wed Mar 18 18:01:04 PDT 2009
    -->

    Now, i don't understand how it is publicly callable yet authentification is needed?
    Is this a bug, or what. Please Help me. From yahoo's own stated logic, this should not happen.
    0
  • QUOTE (Yuval Kesten @ Mar 18 2009, 10:35 PM) <{POST_SNAPBACK}>
    The nested query is the one which needs the authentication - if you'll try the query
    [color="#FF0000"]select * from mybloglog.member where member_id = 2008110507453882
    you'll see that it works!

    BTW - this is my MyBlogLogID...

    Good Luck!


    thank you. I understand the problem now
    0

Recent Posts

in YQL