Skip to content

Access HTTP request headers inside Parse triggers. #3097

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
deepu-tp opened this issue Nov 22, 2016 · 8 comments
Closed

Access HTTP request headers inside Parse triggers. #3097

deepu-tp opened this issue Nov 22, 2016 · 8 comments
Labels
type:feature New feature or improvement of existing feature

Comments

@deepu-tp
Copy link

deepu-tp commented Nov 22, 2016

Hello, is there any way to access the HTTP request headers inside a Parse trigger like afterSave or beforeSave?

Request headers have been added to cloud functions (#1461).

I wanted to track activity in beforeSave and afterSave by way of logs. If a request ID is set by an upstream server (as header say X-Request-Id), then all activity for a given request (beforeSave, afterSave) can be tracked via this request ID.

I'd like your thoughts on this. Currently the headers do not get passed to the trigger handler. But this could easily be achieved.

@flovilmart
Copy link
Contributor

As you mentioned that could be easily achieved. you can go ahead and implement it !

@hatpick
Copy link

hatpick commented Jan 9, 2017

@flovilmart this is exactly what they call flaming in oss development, nice!

@flovilmart
Copy link
Contributor

Not sure to follow, if being sarcastic or not.

@flovilmart
Copy link
Contributor

In any case feel free to implement the feature and open a pull request

@mmarshak
Copy link

And news about adding the header to the triggers?

@iOSDevil
Copy link

+1
I need to perform GeoIP lookup prior to saving a new user registration.

@Mbompr
Copy link

Mbompr commented Oct 21, 2017

I'm interested too, but I have had a quick look at it and it does not seems to be easy.

Things seem to start in handleCreate / handleUpdate of ClassesRouter but I did not manage to understand where these were called.

@flovilmart
Copy link
Contributor

implemented

@mtrezza mtrezza added type:feature New feature or improvement of existing feature and removed type:improvement labels Dec 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:feature New feature or improvement of existing feature
Projects
None yet
Development

No branches or pull requests

7 participants