I have an EpiServer project in which I am using the ContentDeliveryAPI to populate an SPA front-end (Vue).
When the site loads, the landing page gets a 404 error returned from the API (either with friendly URL or by content ID). If I then navigate into sub-pages of the site, the API returns the valid page content - but any navigation back to the landing page results in a 404.
If I try the same API calls in Postman, the correct page data is returned so the issue is only when called from the SPA.
Page "http://local.cms.foundation/" returns 404 in the browser but 200 in Postman
Page "http://local.cms.foundation/blog/" returns 200 in the browser and in Postman
I am using Epi v11.24, ContentDeliveryApi v2.10
We encountered a similar issue when developing an SPS ste in Epi. We struggled to find a resolution to this issue (and several other 'features' caused us issues when developing our SPA).
We ultimately developed our own API to retreive the data from Epi.