We tried adding the extension in the "Easy, no code way" section of this guide. However, this appears to attach to a deployment slot.
Rather than add the extension to all deployment slots, we are adding a rewrite rule to the web.config file. We have placed this rule before the Angular SPA routing rewrite rule and set stopProcessing to false, so the Angular rule should still get processed.
We could have combined both into a single rule by prepending https:// to the Angular rule, but I want to ensure we keep the HTTPS redirect regardless of how the app develops.
We tried adding the extension in the "Easy, no code way" section of this guide. However, this appears to attach to a deployment slot.
Rather than add the extension to all deployment slots, we are adding a rewrite rule to the
web.configfile. We have placed this rule before the Angular SPA routing rewrite rule and setstopProcessingto false, so the Angular rule should still get processed.We could have combined both into a single rule by prepending
https://to the Angular rule, but I want to ensure we keep the HTTPS redirect regardless of how the app develops.