🐛 Bug Report: Executions count and bandwidth not incremented when executing function domain · Issue #8339 · appwrite/appwrite · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I trigger a function using the custom generated url: http://667ddc33e6ea2cfd945c.{url}/ it is not getting registered as usage. Not inside the function, not on the dashboard. But when triggering https://{url}/v1/functions/667ddc33002502a9b799/executions it is.
👍 Expected behavior
It should register the usage of the function both ways. Ideally if custom domain is connected the other way can be blocked (minimizing attack surface and reducing entry points).
👎 Actual Behavior
It actually only registers when triggered this: https://{url}/v1/functions/667ddc33002502a9b799/executions way.
🎲 Appwrite version
Version 1.5.x
💻 Operating system
Linux
🧱 Your Environment
Cloudflare is used for the domain. It is hosted on Hetzner VPS CPX21.
👀 Have you spent some time to check if this issue has been raised before?
👟 Reproduction steps
When I trigger a function using the custom generated url:
http://667ddc33e6ea2cfd945c.{url}/
it is not getting registered as usage. Not inside the function, not on the dashboard. But when triggeringhttps://{url}/v1/functions/667ddc33002502a9b799/executions
it is.👍 Expected behavior
It should register the usage of the function both ways. Ideally if custom domain is connected the other way can be blocked (minimizing attack surface and reducing entry points).
👎 Actual Behavior
It actually only registers when triggered this:
https://{url}/v1/functions/667ddc33002502a9b799/executions
way.🎲 Appwrite version
Version 1.5.x
💻 Operating system
Linux
🧱 Your Environment
Cloudflare is used for the domain. It is hosted on Hetzner VPS CPX21.
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: