system.webServer configuration not always applied when using deployment slots

Question

I have the following scenario

1. Create deployment slot
2. Deploy to deployment slot with web deploy
3. Swap deployment slot and production
4. staticContent mimetypes and customHeaders are (not always) picked up by main app.

It doesn't always happen, and since we run 2 instances I also sometimes get the bug on only one of them.

I can fix this by stopping and starting the app, but that will cause downtime..

Answer 1

Hello,

Thank you for posting here!

Please check that, you are using shared or premium mode of web app. Because these 2 are the supported modes for enabling staged publishing.

Are you getting any error message? Please provide us the same, which will help us to provide you some solutions.

To get detailed error message, enable diagnostic logs for Azure web app. For more information, please refer this link, https://azure.microsoft.com/en-in/documentation/articles/web-sites-enable-diagnostic-log/

You can use kudu console to get error logs also. Please refer these links below,

https://github.com/projectkudu/kudu/wiki/Diagnostic-Log-Stream

https://blogs.msdn.microsoft.com/benjaminperkins/2014/04/01/get-azure-website-deployment-logs-from-kudu/

https://github.com/projectkudu/kudu/wiki/Investigating-issues which might help you.

If you are using any module method, in web.config file, you have to mention that module in system.webserver modules section.

Regards,

Swikruti

If a post answers your question, please click Mark as Answer on that post and Vote as Helpful.