Not sure, else i would've fixed it on the javascript side :) I'm
living in the impression that we parsed it along the url before
somewhere too, and that always seemed to go well ...but maybe i'm
mistaken about that :)
On Jun 17, 2008, at 5:55 PM, Cassie wrote:
Is this just because we are passing the param along in the url as
opposed to
the post body? Or is there some other change we made that I am
forgetting?
- Cassie
On Tue, Jun 17, 2008 at 5:51 AM, Chris Chabot <[EMAIL PROTECTED]>
wrote:
I hope that subject line got your attention :-)
The skinny is this: I've finished putting RESTful adapters into
Partuza,
and i noticed there that the security token parsing was having a
major
meltdown. Further investigation revealed that this was due to the
token
being mangled differently in the rest code then in the old
wireformat code.
The solution was to base64_encode() the encrypted token on the
container
side, and urldecode(base64_decode($token)) on the shindig side.
So that means if you don't update your container's code to do the
same
(base64_encode($st)) Shindig will no longer understand it, and
you'll see a
lot of 'BAD GADGET TOKEN' type of errors.
I've updated both Shindig and Partuza, and tested both the old and
new wire
format, and as long as you svn update them both things are working
peachy
again.
Normally i really despise breaking deployments so my apologies for
that but
unfortunately this change was unavoidable.
On to the good news! Yes there is good news too:
http://partuza.us.chabotc.com/ is now in fact running the RESTful
code! So
if you want to take a gander and kick the tires so to speak, go
take a look!
-- Chris
