Cloudinary service responded with HTTP Code: 500 and HTML instead of JSON about cloudinary_npm

[nadavs]

Thank you for reporting this issue. We will look into it.
Can you please share the code that reached the HTML response of the 500 error?

[laurynas-karvelis]

Thank you! I will do that in the evening as currently have no access to my project from work. Btw, best practise would be to assume that everything could break especially when communicating with external resources (in this case - your HTTP API).

As the error fires in one of the response event callbacks, end developer does not have any control to make it fail-save as it the event callback fires out of try catch scope :(.

[laurynas-karvelis]

The issue which was causing your servers to respond with HTTP 500 status code was that for some reasons binary buffer which I was sending upload_stream()'s object was saved as your temp file in FS, but was not able to process it further properly:

exports.sampleExpressJsAction = function(req, res) {
  var stream = cloudinary.uploader.upload_stream(function (response) {
    // before coming here it dies with error mentioned in my original issue comment
    console.log(response);
  });

  req.on('data', stream.write);
  req.on('end', stream.end);
};

...but... if I save the Buffer first into file and then re-read it passing into upload_stream() stream object in the same manner it WORKS! Completely bizzarre...

Both buffer objects (request and file's) are identical. Have no clue why does it happen.

[laurynas-karvelis]

Fixed in #9

[nadavs]

Thank you for all your contributions and for sharing the code. The pull requests were merged into the master branch and are part of the latest released v1.0.1 of the NPM.
We will make sure that the service avoids returning HTML responses for API requests.