[
https://issues.apache.org/jira/browse/SHINDIG-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stanton Sievers resolved SHINDIG-1756.
--------------------------------------
Resolution: Fixed
Committed revision 1331083. Thanks Brian!
> Identify origination of requests
> --------------------------------
>
> Key: SHINDIG-1756
> URL: https://issues.apache.org/jira/browse/SHINDIG-1756
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
