X-Shindig-St behaves differently when the security token is null between Firefox and WebKit browsers
Review Request #5568 - Created June 25, 2012 and submitted
If we set the X-Shindig-ST header to null in WebKit browsers, it will get interpreted as the String "null" on the server side and cause SecurityTokenExceptions.
Existing JUnits pass.
Review request changed
Updated (June 26, 2012, 5:51 p.m.)
- changed from pending to submitted