Use the HTTP output binding to respond to the HTTP request sender (HTTP trigger). This binding requires an HTTP trigger and allows you to customize the response associated with the trigger's request.
The default return value for an HTTP-triggered function is:
HTTP 204 No Content
with an empty body in Functions 2.x and higherHTTP 200 OK
with an empty body in Functions 1.xImportant
This article uses tabs to support multiple versions of the Node.js programming model. The v4 model is generally available and is designed to have a more flexible and intuitive experience for JavaScript and TypeScript developers. For more details about how the v4 model works, refer to the Azure Functions Node.js developer guide. To learn more about the differences between v3 and v4, refer to the migration guide.
ConfigurationThe options
object passed to the output.http()
method currently doesn't support any properties for model v4.
The following table explains the binding configuration properties that you set in the function.json file.
Property Description type Must be set tohttp
. direction Must be set to out
. name The variable name used in function code for the response, or $return
to use the return value. Configuration
The following table explains the binding configuration properties that you set in the function.json file.
Property Description type Must be set tohttp
. direction Must be set to out
. name The variable name used in function code for the response, or $return
to use the return value. Usage
To send an HTTP response, use the language-standard response patterns.
In .NET, the response type depends on the C# mode:
For Java, use an HttpResponseMessage.Builder to create a response to the HTTP trigger. To learn more, see HttpRequestMessage and HttpResponseMessage.
For example responses, see the trigger examples.
Next steps Additional resources In this articleWas this page helpful?
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4