[jira] [Commented] (USERGRID-99) Allow for the ability to set query parameters that will be sent for all requests

["ryan bridges (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/USERGRID-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14615130#comment-14615130 ] 

ryan bridges commented on USERGRID-99:
--------------------------------------

This has been done for some time.  It is reflected in the Apigee documentation [http://apigee.com/docs/api-baas/content/advanced-query-usage].

The functionality is initialized here:
    https://github.com/apache/incubator-usergrid/blob/master/sdks/html5-javascript/lib/modules/Client.js#L43

And picked up for each request here:
    https://github.com/apache/incubator-usergrid/blob/master/sdks/html5-javascript/lib/modules/Client.js#L78
    https://github.com/apache/incubator-usergrid/blob/master/sdks/html5-javascript/lib/modules/Client.js#L102-L104

> Allow for the ability to set query parameters that will be sent for all requests
> --------------------------------------------------------------------------------
>
>                 Key: USERGRID-99
>                 URL: https://issues.apache.org/jira/browse/USERGRID-99
>             Project: Usergrid
>          Issue Type: Story
>            Reporter: ryan bridges
>            Assignee: ryan bridges
>             Fix For: 1.1
>
>
> The use case would be: You have a key, ID, or other piece of data that needs to be passed in the query string to allow the request to be authenticated, tracked, etc.
> An example would be if you have a secure proxy in front of the API server that requires a user-specific token to access the APIs behind it. an example might look like:
> curl http://api.usergrid.com/app/org/endpoint?token=USERTOKEN



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)