-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Comments
As you mentioned that could be easily achieved. you can go ahead and implement it ! |
@flovilmart this is exactly what they call flaming in oss development, nice! |
Not sure to follow, if being sarcastic or not. |
In any case feel free to implement the feature and open a pull request |
And news about adding the header to the triggers? |
+1 |
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 |
implemented |
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.
The text was updated successfully, but these errors were encountered: