...
| Info |
|---|
You can also access request headers, parameters and body from inside your pipeline called by the API Gateway. For more details see: Pipeline Objects Reference |
File Upload
You can put a single file into the body or multiple files using the multipart/form-data header. In the first case, the upload is provided as single input to the body of the pipeline. The latter provides a content collection to the body of the pipeline.
The file upload works the same way as described for pipelines. For more details see here:
Automation Pipeline and Commands.
Service
This target forwards any request to a microservice deployed inside the cluster and managed by PIPEFORCE. Its mandatory to define the name of this service, the port and the service path to forward the request to.
...
{0} = /customer/123/order
{1} = 123
{2} = order
File Upload
The body of the request and the headers will be forwarded as is to the service. The service can then read the headers and body content similar as it would do if it is directly communicating with the client.
Message
This target forwards the request as a message into the internal message bus on the pipeforce default broker with the routing key as configured. The body of the request will become the payload of the message.
If polling is set to true, a location redirect will be returned to the caller until the final result is available.
File Upload
Only single file upload is supported. The file will be forwarded as byte array in the message to the queue. The Content-Type header of the request will be set to the Content-Type header of the message.
Auth
This toggle enables authentication for this endpoint: If enabled, it will be checked wether a valid Authorization header exists in request and whether the authentication in it is valid. This can be a Bearer token, a Basic (username and password) auth or any other supported authorization value.
...