- Simon Waight
I'm noting this post down in the "if only someone had already made a big noise about this I might have saved some time" category.
The work I'm doing at present involves fronting some APIs with Azure API Management and then exposing them securely.
When I hit the moment I thought I was done today I was doing some testing, and no matter what I did I couldn't get my backend service to respond, and I could clearly see no traffic hitting the backend.
After double-checking my policies and doing a few more tests (only a couple of hours) I then happened across this Stack Overflow question and its answer...
It turns out that I had, somewhere along the line, removed the "forward-request" policy from the Policy applying to all APIs published via API Management.
So how to fix? As Darrell says, find the offending Policy and add the missing item back.
When done it should like the image below.
... and your API calls will now work as expected and not just give you back 200 OK! 😎