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
The documentation shows how to invoke HTTP-triggered functions. It shows Azure Storage Queues for non-HTTP functions, but that scenario is straightforward because the data posted is transformed into the Storage Queue payload as-is. With ASB, custom headers (application properties) can also be passed in addition to the message payload. Is it possible to achieve passing headers + body for the message? And if 'yes', what's the correct syntax?
@zvrba, did you read the referenced documentation?
You can also run a non-HTTP function locally using REST by calling a special endpoint called an administrator endpoint. Use this format to call the admin endpoint and trigger a specific non-HTTP function
What you're showing is not an admin endpoint invocation, which is what this question is about.
The documentation shows how to invoke HTTP-triggered functions. It shows Azure Storage Queues for non-HTTP functions, but that scenario is straightforward because the data posted is transformed into the Storage Queue payload as-is. With ASB, custom headers (application properties) can also be passed in addition to the message payload. Is it possible to achieve passing headers + body for the message? And if 'yes', what's the correct syntax?
Original question from StackOverflow.
The text was updated successfully, but these errors were encountered: