Scenario:
I have two APIM instances deployed in my environment.
- hosted in internet segment within first virtual network
- hosted in intranet segment within second virtual network
- peering is enabled between vnets.
Note: I do not have any issue while testing my api hosted in intranet, which in turn call the backend services (azure app service - webapp)
forward-request (152.089 ms)
{
"response": {
"status": {
"code": 403,
"reason": "Forbidden"
},
"headers": [
{
"name": "Vary",
"value": "Origin"
},
{
"name": "Access-Control-Allow-Origin",
"value": "https://apimanagement.hosting.portal.azure.net"
},
{
"name": "Access-Control-Allow-Credentials",
"value": "true"
},
{
"name": "Access-Control-Expose-Headers",
"value": "Content-Length,Vary"
},
{
"name": "Content-Length",
"value": "45"
},
{
"name": "Content-Type",
"value": "application/json"
},
{
"name": "Date",
"value": "Thu, 15 Jul 2021 01:52:44 GMT"
}
]
}
}
Outbound
(1.214 ms)↑ Back to top
cors (0.062 ms)
{
"message": "Headers starting with 'Access-Control-' were removed from the response. ",
"headers": [
{
"name": "Vary",
"value": "Origin,Origin"
},
{
"name": "Access-Control-Allow-Credentials",
"value": "true"
},
{
"name": "Access-Control-Expose-Headers",
"value": "Vary,Content-Length,Date,Ocp-Apim-Trace-Location"
}
]
}
transfer-response (1.152 ms)
{
"message": "Response has been sent to the caller in full"
}
@Mayank , Yes we do not have support plan.
For time being, I have kept this task on hold.
Thank you for your kind support and follow-up on this issue.
@Madala, Hanumantharao Thanks for your response. Please tag me in once you resume/ need any assistance and I would assist you further.