Characteristics of HTTP API Gateway triggers:
eventtype format conversion. HTTP request information includes the specific service that receives the request, API rule, actual request path, method, and
queryof the request.
In API Gateway, one API rule can be bound to only one function, but one function can be bound to multiple API rules as the backend. You can create an API with different paths in the API Gateway console and point the backend to the same function. APIs with the same path, same request method, and different release environments are regarded as the same API and cannot be bound repeatedly.
Request method is the method to process request sent from API Gateway to SCF, and response method is the method to process the returned value sent from SCF to API Gateway. For web functions, API Gateway will add the information required for function triggering in the
header and directly pass through the original request to trigger the backend function.
The following parameters don't support custom configuration:
- Custom fields starting with