Proxy request to Teneo engine
POST/proxy
Proxies requests to a Teneo engine specified in the engine header.
Key Behaviors
- Session Header Construction:
sessionIdandgatewayfields are removed from the body and combined into theX-Teneo-Sessionheader format:JSESSIONID=<sessionId>;gateway - Parameters Parsing: If
parametersis provided as a JSON string, it's parsed and spread into the request body at the root level - Session Termination: When
isTerminatingSessionistrue, the session will be ended by this request. - Gateway Response Mapping: The
X-Gateway-Sessionresponse header from the engine is mapped to agatewayfield in the response body
Request Flow
- Validates
Content-Typeheader (must beapplication/json) - Transforms request body (removes
sessionId/gateway, parsesparameters) - Constructs
X-Teneo-Sessionheader fromsessionIdandgateway - Forwards request to the Teneo engine
- Maps
X-Gateway-Sessionresponse header togatewayfield in response body - Returns the transformed response
Request
Responses
- 200
- 400
- 415
- 500
Successful proxy response
Bad Request - Invalid or missing engine header
Unsupported Media Type - Content-Type must be application/json
Internal Server Error - Failed to proxy request to engine