We've got an issue with the headless content api, in some cases.
Everything works fine while we're running local dev on IIS Express, both firendly-url (which our Angular app relies on) as well as /api/episerver/v2.0/content/XXXX requests works. However, after deploying to Azure, we get a 404 Not Found from the content api-request. Though making the same CURL request to https://AZURE/api/episerver/v2.0/content/XXXX does work. So it seems like the content-api works, but there's some configuration differences web server-wise.
We've managed to reproduce the error locally by setting up a stand alone IIS server for the site, but it's a bit hard to debug this issue. Does anyone have any suggestions what could be causing this?
We've followed setup and configuration:
https://world.episerver.com/documentation/developer-guides/content-delivery-api/configuration/
https://world.episerver.com/documentation/developer-guides/content-delivery-api/using-friendly-urls/
- Latest version (ContentApi 2.4.0, no search, no OAuth)
- Utilizing Friendly urls (Accept headers, content-type 'application/json' and language are set)