Thanks for the great Feedback, Sergio!

Late last night I noticed that I missed the @convertResponseToBase64 parameter and submitted a fix for the article. I also just now submitted a fix for the other issue you pointed out.

Since I first submitted this article I've made some changes to the function I would like to post soon. Notably, I've added some error handling and I also changed the parameters to include a generic "options" parameter to pass in the things like timeout, base64 encoding, etc. Thought being if more features are added in over time and it requires adding new parameters that will break existing code since SQL Server requires all parameters to be specified when calling a function. A single "options" parameter that allows you to pass in various features you'd like to utilize solves that issue.