[
https://issues.apache.org/jira/browse/SHINDIG-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Lindner resolved SHINDIG-193.
----------------------------------
Resolution: Fixed
applied
> Small bug in timestamp key / contains key checking
> --------------------------------------------------
>
> Key: SHINDIG-193
> URL: https://issues.apache.org/jira/browse/SHINDIG-193
> Project: Shindig
> Issue Type: Bug
> Components: Gadget Rendering Server (Java)
> Reporter: Chris Chabot
> Priority: Minor
> Attachments: SHINDIG-193.patch
>
>
> In BasicBlobCrypter there is a TIMESTAMP_KEY which theoretically you could
> change to anything you want, except that the error generated if this key is
> present in the to-be-encrypted array has a hard coded 't' value:
> if (in.containsKey(TIMESTAMP_KEY)) {
> throw new IllegalArgumentException("No 't' keys allowed for
> BlobCrypter");
> }
> This should really be changed to use the TIMESTAMP_KEY too, so we don't end
> up having very confusing error messages somewhere in the future :-)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
