You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@shindig.apache.org by "Evan Gilbert (JIRA)" <ji...@apache.org> on 2009/08/03 18:45:14 UTC

[jira] Reopened: (SHINDIG-606) Move security token to header for XMLHttpRequests?

     [ https://issues.apache.org/jira/browse/SHINDIG-606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Evan Gilbert reopened SHINDIG-606:
----------------------------------

      Assignee:     (was: Evan Gilbert)

We're still sending the long-lived token on the URL on XMLHttpRequests for data. It would be easy to move this to a header and would improve security - headers usually aren't logged.

> 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
>
> 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.