08-08-2010 02:51 PM
Still no luck for me. For those that got it to work, did you just change the URLUTF8Encoder class result by adding toUpperCase at the end to the whole string?
Could someone post theirs?
08-11-2010 08:58 PM
Just an update.. I did get it working the other day. Turns out that it was a typo in my header building method. Using the netflix tool really helped though for seeing what signature to expect throughout the debugging process.
08-16-2010 05:37 AM
08-19-2010 03:39 PM - edited 08-19-2010 03:41 PM
I too get the signature
MUYmiobRdoK6s0ZVqo4xQNNO17w%3D (after url encoding)
when signing the exact string from the example.. did this turn out to be 'ok' or was there a mistake that prevented you from getting the exact same string of yUDBrcMMm6ghqBEKCFKVoJPIacU%3D ?
08-19-2010 03:49 PM
I do not think you get the same string as they do. I get the same string everytime I encode on my machine, but I think it is different form what you would get on any other machine.
Best I can tell anyway.
08-19-2010 03:58 PM
Ok, dumb mistake on my end.. the header name is Authorization not OAuth, as in
and to answer my own question, getting the different signature for the same string is apparently fine.