Google Firebase Functions - Timeout when doing HTTP requests

Question

So I am trying to make a simple proxy (I think that's the right word) and I've come up with some code that works fine locally. I can call 'firebase serve --only functions' and the function works fine and I get expected results. Now when I deploy this same code, and try calling it it just times out. I have no idea why, so I was hoping I could get some help.

Here's the code:

//Variables
const functions = require('firebase-functions');
const express = require('express');
const cors = require('cors');
const request = require('request');

//App
const app = express();
app.use(cors({ origin: true }));

//Endpoints
app.get('/**', function(req, res) {
    request('https://example.com' + req.url, function(err, proxyRes, body) {

        //Err
        if (err) {
            res.send('Error: ' + err.code);
            return
        }

        //Res
        res.status(200).send(body);
    });
});

//Functions
exports.proxy = functions.https.onRequest(app);

Doug Stevenson · Accepted Answer · 2018-04-26 18:38:20Z

1

HTTP functions will time out if they don’t send a response. This means your request() is probably failing, and it’s probably failing because, on the free Spark payment plan, you can’t make outgoing requests to services that Google doesn’t fully control.

Your function should send a response in all conditions in order to avoid a timeout. This means you should be checking for errors all the time.

answered Apr 26, 2018 at 18:38

Doug Stevenson

321k37 gold badges458 silver badges474 bronze badges

Sign up to request clarification or add additional context in comments.

6 Comments

Sean Over a year ago

I'm on the Blaze plan, not the spark plan.

Doug Stevenson Over a year ago

You still need to be checking for errors and sending a response back to the client in all circumstances.

Sean Over a year ago

How would I do that, I updated the code but it's still showing the same error. Updated the original post

Doug Stevenson Over a year ago

It's entirely possible also that the request is taking longer than the default timeout of 60 seconds for a Cloud Function. The only way you can know that is to increase the timeout in the cloud console, or impose a timeout on your own request to stop before 60s.

Doug Stevenson Over a year ago

Also you might want to consider logging things so you can see what parts of your code are actually being accessed. Without logs, you are really just guessing what's happening.

|

Collectives™ on Stack Overflow

Google Firebase Functions - Timeout when doing HTTP requests

1 Answer 1

6 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

6 Comments

Your Answer

Sign up or log in

Post as a guest

Related