shindig-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stanton Sievers (JIRA)" <>
Subject [jira] [Commented] (SHINDIG-1756) Identify origination of requests
Date Fri, 27 Apr 2012 15:22:49 GMT


Stanton Sievers commented on SHINDIG-1756:

Missed during the initial commit.  Committed revision 1331466.
> Identify origination of requests
> --------------------------------
>                 Key: SHINDIG-1756
>                 URL:
>             Project: Shindig
>          Issue Type: Improvement
>          Components: Java
>    Affects Versions: 2.5.0
>            Reporter: Brian Lillie
>             Fix For: 2.5.0
>         Attachments: origination5.patch
> In order to determine based upon the request whether to honor the request, or whether
the request should be restricted, the request needs to identify itself in some way.    Some
of the requests in the system originate as a result of direct user requests (e.g. makeRequest)
while other requests are performed by the server for the server or in order to handle the
request (e.g. gadget spec lookups).
> The proposal is to better mark the origination of the request either by attaching an
Anonymous Security Token containing the gadget URI, or by marking the request as an internal
request (one that the server is initiating) so that downstream components (e.g. the HttpFetcher
implementation) can make determinations on how to process the request.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message