Utilizing SSR in conjunction with APIM on SWA

[sb-sh]

Hey Geoff--appreciate all the work on SvelteKit and the SWA adapter.

Perhaps I am missing something (still fairly new to SvelteKit), but I have linked Azure API Management to my SWA instance, and in doing so have seemingly removed the ability to SSR any of my pages (as all requests to /api are proxied to APIM). Unsure of how common this is.

Is this something that can be contemplated in the adapter (maybe changing the routing for the page render)? Or, am I better off writing a standalone render function and sticking it behind my APIM instance?

Thanks

[geoffrich]

Hey, unfortunately this isn't a use case I'm familiar with. I'm unclear on why proxying the /api route to APIM would make it so the /api/__render request is not handled properly. Do you know what staticwebapp config change would be required?

svelte-adapter-azure-swa/index.js

Lines 217 to 219 in 9b4d834

	navigationFallback: {
	rewrite: ssrFunctionRoute
	},

[sb-sh]

Apologies for the several month delay here.

It may well be a config issue/misunderstanding on my part. I have a project that uses existing APIs that are orchestrated in APIM to render data on the page. So, I just linked my SWA to my APIM instance. Now, with everything sent to /api being proxied to APIM, and no way to exclude certain routes, I either need to define a _render function within my APIM instance (and likely create an Azure Function behind it), or figure out how to change the ssrFunctionRoute in svelte-adapter-azure-swa so that the __render request doesn't proxy to my APIM instance.

It may be just as simple as optionally changing the ssrFunctionRoute /api/_render to /newname/_render to keep things local.

Thank you!