req.headers is undefined

[nirco123]

Hi All,

Any reason why the req.headers is undefined, we would love to get the request IP and it seems impossible without the headers, I tried search the code and the headers are been overwrite, any specific reason for that?

Thanks.

[steven-supersolid]

Assuming you mean in Cloud Code - this is the case on Parse.com but it is a bit limiting, e.g. we currently send the user agent information as part of a request as it is unavailable in the header.

The request object is not a node request object but Parse.Cloud.FunctionRequest
https://parse.com/docs/js/api/classes/Parse.Cloud.html#methods_define
I'd also like to know the reasoning behind this.

[nirco123]

Yes, but since we are not on Parse.com hosting any more im trying to understand if there is any reason not using headers in the request .

[andyburgess1978]

I've anted to do something similar for ages, but until the parse server came along there wasn't a way to do it.
I haven't been able to get the headers in the cloud/main.js file so I've added routes that handle the IP detection and then forward that on to the cloud code using Parse.Cloud.run calling the cloud function.

app.post('/push', function(req, res) {
var ip = req.headers['x-forwarded-for'] || req.connection.remoteAddress || req.socket.remoteAddress || req.connection.socket.remoteAddress;
var data = {ips:ip};
Parse.Cloud.run('functionname', data, {
        success: function(response) {
          res.json({success: true, result:response});
        },
        error: function(error) {
          res.json({success: false, error:error});
        }
      });
}

[drew-gross]

We didn't do this because we were aiming for compatibility with Parse.com. It seems like there is interest, though, and I don't see any reason not to add it.

[tarekskr]

Any updates on this? I think it's really vital to allow access to the request's headers from Cloud Code.

[ritterb82]

+1

[greggmojica]

+1

[tarekskr]

@greggmojica this has already been implemented 👍

[greggmojica]

@tarekskr I actually just saw that. My bad. Thanks!!

[crifkin]

@tarekskr the fix posted for #1461 doesn't appear to be true for Triggers. I see the code that adds this for Functions, but the method that headers would be injected for Triggers (before/afterSave, etc) is much more involved and I've spent several hours digging through code to try to find the place to put this in, so if you see a clear path, please provide guidance or help. thx.

[flovilmart]

@crifkin sorry for the late response.

Yes it needs more work to be able to forward the request headers to the hooks.

I've prioritized it and we should be able to do something for that.

[miguel-s]

@flovilmart I can take this issue, we have a working solution on our local branch and wouldn't take too long to create a pull request

[flovilmart]

@miguel-s feel free to do so! I’ll review the Pr!

[flovilmart]

Closing as PR is merged stay tuned for next release