[
https://issues.apache.org/jira/browse/SHINDIG-606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Chabot resolved SHINDIG-606.
----------------------------------
Resolution: Fixed
I believe this has been dealt with on atleast some containers by using a short
lived token on the url, and injecting a longer lived token through the gadgets
js config, so this issue doesn't seem topical anymore (please reopen if it is)
> Move security token to header for XMLHttpRequests?
> --------------------------------------------------
>
> Key: SHINDIG-606
> URL: https://issues.apache.org/jira/browse/SHINDIG-606
> Project: Shindig
> Issue Type: Improvement
> Components: Java, PHP
> Reporter: Evan Gilbert
> Assignee: Evan Gilbert
>
> It seems slightly more secure if the security token were put into an HTTP
> header instead of in the URL when making requests back to the server from
> gadgets. This way the token is not normally logged by proxies, etc.
> We'd still probably support the URL parameter for debugging purposes.
> I'm not a security expert, possibly others with more experience can weigh in
> on how important this is.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
