making an https request inside of an azure function

Question

I'm attempting a simple request:

var options = {
                host: 'hookb.in',
                path: '/8PMoEa9kbaCXgXYxOmdr5',
                method: 'POST'
            };

            var req = http.request(options, (res) => {
                var body = context.bindingData.name;

                res.on("data", (chunk) => {
                    body += chunk;
                });

                res.on("end", () => {
                    context.res = body;
                });
            }).on("error", (error1) => {
                context.log('error');
                context.res = {
                    status: 500,
                    body: error1
                };
            });
            req.end();
            context.done();

However, there's no response (and no request received by the target here https://hookbin.com/8PMoEa9kbaCXgXYxOmdr).

What am I doing wrong? Is there a special way to create an https request inside of an azure function?

var Jimp = require("jimp");
var http = require('https');

module.exports = async function (context, myBlob) {
    context.log("JavaScript blob trigger function processed blob \n Name:", context.bindingData.name, "\n Blob Size:", myBlob.length, "Bytes");
    context.log(process.env.ImageConvertedWebHook);
    Jimp.read(myBlob, function (err, image) {
        image.getBufferAsync(Jimp.MIME_TIFF, function (error, imageData) {
            context.log('Node.JS blob trigger function resized ' + context.bindingData.name + ' to ' + image.bitmap.width + 'x' + image.bitmap.height);
            context.bindings.outputBlob = imageData;

            var options = {
                host: 'hookb.in',
                path: '/8PMoEa9kbaCXgXYxOmdr5',
                method: 'POST'
            };

            var req = http.request(options, (res) => {
                var body = context.bindingData.name;

                res.on("data", (chunk) => {
                    body += chunk;
                });

                res.on("end", () => {
                    context.res = body;
                });
            }).on("error", (error1) => {
                context.log('error');
                context.res = {
                    status: 500,
                    body: error1
                };
            });
            req.end();
            context.done();
        });
    });
};

I've also attempted this way:

    const data = 'buy milk biotch';
    var options = {
        host: 'hookb.in',
        path: '/8PMoEa9kbaCXgXYxOmdr',
        method: 'POST',
        port: 443,
        headers: {
            'Content-Type': 'application/json',
            'Content-Length': data.length
        }
    };
    const req = https.request(options, res => {
        context.log(`statusCode: ${res.statusCode}`)

        res.on('data', d => {
            context.log(d)
        })
    })

    req.on('error', error1 => {
        context.log(error1)
    })

    req.write(data)
    req.end()

Couple questions: Are you using Functions v1 or v2? Also, is this an async function? — PerfectlyPanda, Aug 24 '19 at 18:31
Do you have a specific reason you do not use npm package `request` and `request-promise`? — Farrukh Normuradov, Aug 25 '19 at 09:56
I was a little kid when I immigrated out of Russia. Your name is very interesting — Alex Gordon, Aug 26 '19 at 12:49

score 3 · Answer 1 · answered May 07 '20 at 04:30

This is a working example of how to request Azure AD v2 endpoint to get access token inside of your Azure Function V3 (node runtime)

var http = require('https');

module.exports = function (context, req) {
    var body = "";
    body += 'grant_type=' + req.query['grant_type'];
    body += '&client_id=' + req.query['client_id'];
    body += '&client_secret=' + req.query['client_secret'];
    body += '&code=' + req.query['code'];

    const options = {
        hostname: 'login.microsoftonline.com',
        port: 443,
        path: '/ZZZZZZZZ-bc69-4c8b-8e91-11f3a181c2bb/oauth2/v2.0/token',
        method: 'POST',
        headers: {
            'Content-Type': 'application/x-www-form-urlencoded',
            'Content-Length': body.length
        }
    }

    var response = '';
    const request = http.request(options, (res) => {
        context.log(`statusCode: ${res.statusCode}`)

        res.on('data', (d) => {
            response += d;
        })

        res.on('end', (d) => {
            context.res = {
                body: response
            }
            context.done();
        })
    })

    request.on('error', (error) => {
        context.log.error(error)
        context.done();
    })

    request.write(body);
    request.end();
};

Differences between this and OP's: function is not marked as async (module.exports = function) and I'm using context.done(); to let the runtime know when an async action (https request in our case) is done. context.done(); is in two places: 'end' and 'error' callbacks.

I believe async/await + promises should be used instead of callbacks if you want to use an async function - link

Using the async and await keywords helps avoid both of these errors. You should use the Node.js utility function util.promisify to turn error-first callback-style functions into awaitable functions.

Not a JS dev.

score 1 · Accepted Answer · answered Jun 23 '22 at 07:27

1

I had the same issue but after removing async from module.exports = async function (context, myBlob), this should be work. If you want to treat this as a async function, this might be helpful.

answered Jun 23 '22 at 07:27

Sashini Hettiarachchi

1,630
2
10
21

score 0 · Answer 3 · answered Aug 25 '19 at 11:33

Seems like naming conflict issue .Couple of variables to change in your code:

Change below

var http = require('https');

To

var httpMod = require('https');

Change below

const req = https.request(options, res => {
            context.log(`statusCode: ${res.statusCode}`)
    
            res.on('data', d => {
                context.log(d)
            })
        })

To

 const customReq = httpMod.request(options, res => {
            context.log(`statusCode: ${res.statusCode}`)
    
            res.on('data', d => {
                context.log(d)
            })
        })

Hope it helps.

As shown by aderesh's answer, Microsoft examples use 'http' as the variable name with no conflict. The 'async' keyword is likely the issue. — PoorInRichfield, Apr 16 '21 at 15:34

making an https request inside of an azure function

3 Answers3

Linked