Invalid Signature after upload request from PARSE

Follow

Stephane Giloppe

• April 17, 2014 21:03

The title says it all.

I have requested an upload and got a valid JSON. (I replaced actual signatures, api_keys and name with dummy ones for this post). Basically, the 2 CURL commands are executed within seconds of each other and I pay attention to use the same timestamp and signature.

{"result":

{"timestamp":1397768188,

"eager":"c_fill,g_face,h_100,w_150",

"tags":"Steph",

"signature":"dummySignatureHere",

"api_key":"dummyAPIKeyHere"}}

Then I used this exact command:

curl -X POST \

  -F timestamp=1397768188 \

  -F tags=Steph \

  -F signature=dummySignatureHere \

  -F api_key="dummyAPIKeyHere" \

  -F file=@poisson.jpg \

  http://api.cloudinary.com/v1_1/dummyName/image/upload

Any help is appreciated.

 

Thanks.

0

• 

  Itay Taragano

  • April 17, 2014 21:54

  Hi Stephane,

  It seems that while the eager transformation is being signed, it wasn't passed in the request to Cloudinary.

  0

  Comment actions Permalink
• 

  Stephane Giloppe

  • April 21, 2014 22:03

  It was exactly that Itay. Thank you.

  Not only you provided the solution, but you gave me insight into the whole mechanism. So, I understand that all that happen server side will come back in the signature request and will need to be passed along to the upload request.

   

  Thanks.

  0

  Comment actions Permalink

Please sign in to leave a comment.