1 Reply Latest reply on Dec 9, 2015 8:23 AM by kevin_gu

    Jive rest response contains an extra line that break the json format

    kevin_gu

      Hi guys,

       

      I found that whenever I do a rest call to jive the response i receive will have an extra line "throw 'allowIllegalResourceCall is false.';"(in red):  you can reproduce it by doing any GET request, for this example i did "https://otpp-2.jiveon.com/api/core/v3/people/email/kevin_gu@otpp.com?fields=name"

       

      this will break the json parsing at our side because this is no longer a valid json format response.

       

      "

      throw 'allowIllegalResourceCall is false.';

      {

        "id" : "52104",

        "resources" : {

        "reports" : {

        "allowed" : [ "GET" ],

        "ref" : "https://otpp-2.jiveon.com/api/core/v3/people/52104/@reports"

        },

        "followingIn" : {

        "allowed" : [ "POST", "GET" ],

        "ref" : "https://otpp-2.jiveon.com/api/core/v3/people/52104/followingIn"

        },

        "images" : {

        "allowed" : [ "GET" ],

        "ref" : "https://otpp-2.jiveon.com/api/core/v3/people/52104/images"

        },

        "activity" : {

        "allowed" : [ "GET" ],

        "ref" : "https://otpp-2.jiveon.com/api/core/v3/people/52104/activities"

        },

        "manager" : {

        "allowed" : [ "GET" ],

        "ref" : "https://otpp-2.jiveon.com/api/core/v3/people/52104/@manager"

        },

        "social" : {

        "allowed" : [ "GET" ],

        "ref" : "https://otpp-2.jiveon.com/api/core/v3/people/52104/@social"

        },

        "recognition" : {

        "allowed" : [ "GET" ],

        "ref" : "https://otpp-2.jiveon.com/api/core/v3/people/52104/@recognition"

        },

        "trendingContent" : {

        "allowed" : [ "GET" ],

        "ref" : "https://otpp-2.jiveon.com/api/core/v3/people/52104/@trendingContent"

        },

        "trendingPlaces" : {

        "allowed" : [ "GET" ],

        "ref" : "https://otpp-2.jiveon.com/api/core/v3/people/52104/@trendingPlaces"

        },

        "avatar" : {

        "allowed" : [ "GET" ],

        "ref" : "https://otpp-2.jiveon.com/api/core/v3/people/52104/avatar?a=1019"

        },

        "followers" : {

        "allowed" : [ "GET" ],

        "ref" : "https://otpp-2.jiveon.com/api/core/v3/people/52104/@followers"

        },

        "colleagues" : {

        "allowed" : [ "GET" ],

        "ref" : "https://otpp-2.jiveon.com/api/core/v3/people/52104/@colleagues"

        },

        "following" : {

        "allowed" : [ "GET" ],

        "ref" : "https://otpp-2.jiveon.com/api/core/v3/people/52104/@following"

        },

        "members" : {

        "allowed" : [ "GET" ],

        "ref" : "https://otpp-2.jiveon.com/api/core/v3/members/people/52104"

        },

        "self" : {

        "allowed" : [ "GET" ],

        "ref" : "https://otpp-2.jiveon.com/api/core/v3/people/52104"

        },

        "html" : {

        "allowed" : [ "GET" ],

        "ref" : "https://otpp-2.jiveon.com/people/kevingu"

        },

        "extprops" : {

        "allowed" : [ "GET" ],

        "ref" : "https://otpp-2.jiveon.com/api/core/v3/people/52104/extprops"

        }

        },

        "name" : {

        "familyName" : "Gu",

        "formatted" : "Kevin Gu",

        "givenName" : "Kevin"

        },

        "type" : "person",

        "typeCode" : 3

      }

      "

       

      Is this a bug? or just a config thing at your side? or we need to put something into our header?

       

      Thanks,

       

       

      Kevin