Geoff Rich

> It's really strange why the header is not there on some requests. I have the same app running with Remix using [@derkoe/remix-azure-functions](https://github.com/derkoe/remix-azure-functions) and there the auth works with locally...

Theorizing: maybe the rewrite has something to do with it, and Azure preemptively filters out cookies that don't match the current path (which was re-written to /__sk_render).

Yep, confirmed in #113 that is the case. So if we wanted to make that switch, we'd have to add routing rules for anything in `static` and any prerendered files....

Once alternate approach to force the client principal header in local dev is middleware like this that fetches the `/.auth/me` endpoint and manually attaches the `x-ms-client-principal` header (extended from the...

Also, as a note for the eventual documentation: we should provide multiple configurations for dev time (point everything at 5173) and "production" (point at the built app). Something like: ```json...

Ah, good find! Though when I originally ran into this issue it doesn't appear like I was setting a max-age at all. It's been a bit; I'll try to find...

Thanks for the feedback! > If the user doesn't set allowedRoles for a route, they may have set it at the top level of the config object to apply to...

I'm open to having this in the adapter itself, if you're willing to submit a PR. Having accurate URLs in App Insights is important. If I'm understanding correctly, we'd want...

Azure announced preview support for Node.js streams: https://techcommunity.microsoft.com/t5/apps-on-azure-blog/azure-functions-support-for-http-streams-in-node-js-is-now-in/ba-p/4066575

Putting "help wanted" on this, in case someone wants to try updating the adapter themselves. I'll get to it eventually but not sure when I'll have time.