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
It would be nice to restrict invocation to requests containing a secret in a header (X-Invocation-Token). This can be implemented in the deployment's code instead, but unauthorized public requests would still result in invocations (that have a cost).
The text was updated successfully, but these errors were encountered:
Sounds like a use case for a „private“ FaaS which is only accessible within the Deno Deploy network from other FaaS in your account. The benefit over a „public“ FaaS which is accessible through the open Internet is that it doesn’t need authentication which would complicate your code. Also it is safer because a door can’t be breached if there is no door.
See proposal #88 for more details on a single-instance private FAAS and a multi-instance private FAAS in the “Future” section.
It would be nice to restrict invocation to requests containing a secret in a header (X-Invocation-Token). This can be implemented in the deployment's code instead, but unauthorized public requests would still result in invocations (that have a cost).
The text was updated successfully, but these errors were encountered: