Right now, I cannot figure out how to get the X-Forwarded-For and [insert the header my proxy uses for specifically the client's ip here] headers when the function is called with functions.createExecution. Is there any way I can get the client IP when the function is created from createExecution rather than a regular http request? And is there any way I can specify which headers should just be passed through to the function from the original request (that are added by my proxy)?
As of now, the client can just say "yeah my ip is 1.2.3.4" when its actually 2.3.4.5 (example ips ofc) by simply calling createExecution with those headers - or it can just pretend not to have an IP. I'm not sure how I should fix this.
Recommended threads
- Appwrite-injected variables are not avai...
I am using rust-1.83 as a runtime and try to access APPWRITE_FUNCTION_API_ENDPOINT or APPWRITE_FUNCTION_API_KEY during runtime. Both are not set during my execu...
- Functions in cloud console not works
please advise as all of my runing functions on Appwrite console was working before , but now it give this error [Invalid `headers` param: Value must be a valid...
- [SOLVED] Production down - createExecuti...
Hey, Since 1.9.6 rollout in fra (~17:00 UTC, 14 Aug), POST /v1/functions/{functionId}/executions returns a 400 whenever the body includes an empty headers ob...