You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by "Adam Winer (JIRA)" <ji...@apache.org> on 2008/11/06 00:26:44 UTC

[jira] Created: (SHINDIG-676) When security token not present, RPC requests contain "?st=null"

When security token not present, RPC requests contain "?st=null"
----------------------------------------------------------------

                 Key: SHINDIG-676
                 URL: https://issues.apache.org/jira/browse/SHINDIG-676
             Project: Shindig
          Issue Type: Bug
          Components: Features (Javascript)
            Reporter: Adam Winer
            Priority: Minor
         Attachments: shindig-676.patch

If you omit the security token from an iframe, subsequent json RPC requests should omit the security token parameter, and let the container deal.  Instead, it sends "?st=null", which looks like a malformed security tokenl.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (SHINDIG-676) When security token not present, RPC requests contain "?st=null"

Posted by "Adam Winer (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SHINDIG-676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adam Winer updated SHINDIG-676:
-------------------------------

    Attachment: shindig-676.patch

Attached patch.

> When security token not present, RPC requests contain "?st=null"
> ----------------------------------------------------------------
>
>                 Key: SHINDIG-676
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-676
>             Project: Shindig
>          Issue Type: Bug
>          Components: Features (Javascript)
>            Reporter: Adam Winer
>            Priority: Minor
>         Attachments: shindig-676.patch
>
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> If you omit the security token from an iframe, subsequent json RPC requests should omit the security token parameter, and let the container deal.  Instead, it sends "?st=null", which looks like a malformed security tokenl.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (SHINDIG-676) When security token not present, RPC requests contain "?st=null"

Posted by "Paul Lindner (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SHINDIG-676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Lindner resolved SHINDIG-676.
----------------------------------

    Resolution: Fixed

thanks, committed.


> When security token not present, RPC requests contain "?st=null"
> ----------------------------------------------------------------
>
>                 Key: SHINDIG-676
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-676
>             Project: Shindig
>          Issue Type: Bug
>          Components: Features (Javascript)
>            Reporter: Adam Winer
>            Priority: Minor
>         Attachments: shindig-676.patch
>
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> If you omit the security token from an iframe, subsequent json RPC requests should omit the security token parameter, and let the container deal.  Instead, it sends "?st=null", which looks like a malformed security tokenl.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.