Home/ Questions/Q 8605405
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-12T02:49:20+00:00

Adding to my web.config <system.webServer> <staticContent> <mimeMap fileExtension=.json mimeType=application/json /> </staticContent> </system.webServer> Allows my

  • 0

Adding to my web.config

<system.webServer>
  <staticContent>
    <mimeMap fileExtension=".json" mimeType="application/json" />
  </staticContent>
</system.webServer>

Allows my application to run on Azure, but will crash my remote IIS server because its already included. Removing the remote IIS mimeType is not practical in this particular case. I end up using a different web.config

Is there another mechanism by which I can configure Azure IIS mimeType so I don’t have this problematic web.config?

I would like a single deployment package that will work on Azure and non Azure.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    This should work:

    <system.webServer>
  <staticContent>
    <remove fileExtension=".json" />
    <mimeMap fileExtension=".json" mimeType="application/json" />
  </staticContent>
</system.webServer>

    See also here: http://blogs.msdn.com/b/chaun/archive/2009/12/04/iis7-error-cannot-add-duplicate-collection-entry-of-type-mimemap-with-unique-key-attribute-fileextension.aspx

    This doesn’t make any difference to your overall IIS configuration, it just conditionally removes the mimeMap from the configuration of this particular site (as governed by this web.config) before adding it again.

    • 0