Usage of Host header in TIBCO Mashery
Article ID: KB0073652
Updated On:
| Products | Versions |
|---|---|
| TIBCO Cloud API Management | ALL |
Description
#Configuration
When configuring an endpoint in Mashery only one host/ip can be provided in the Public Endpoint(CloudMashery) or Published Endpoint(MasheryLocal-Untethered).
However there can be multiple TM's that can handle the request:
- multiple workers/load balancing domains in CloudMashery
- multiple TMs in Mashery Local(Tethered as well as Untethered)
#Issue
If the public endpoint is:
https://<public_host/ip>/<path/uri>
and a particular TM receives the request as:
https://<tm_host/ip>/<path/uri>
then it will return 596 Service Not Found error.
When configuring an endpoint in Mashery only one host/ip can be provided in the Public Endpoint(CloudMashery) or Published Endpoint(MasheryLocal-Untethered).
However there can be multiple TM's that can handle the request:
- multiple workers/load balancing domains in CloudMashery
- multiple TMs in Mashery Local(Tethered as well as Untethered)
#Issue
If the public endpoint is:
https://<public_host/ip>/<path/uri>
and a particular TM receives the request as:
https://<tm_host/ip>/<path/uri>
then it will return 596 Service Not Found error.
Issue/Introduction
This article provides inputs on the usage of Host header when calling a Mashery endpoint and avoid 596 Service Not Found error
Environment
All Supported Platforms.
Resolution
To resolve this error, the value for the Host header should match the one in the public/published endpoint
- while the request is sent to the handling TM.
- while the request is sent to the handling TM.
Feedback
Yes
No
Powered by
