Server Configuration
From Svg wiki
Server misconfiguration is a common reason for SVG failing to load. Servers must identify SVG with the correct MIME type (image/svg+xml) and tell clients if the SVG is stored gzipped. This is done using HTTP headers. For security and correctness reasons, some browsers decide how to handle files only by looking at the HTTP headers the server sends with them. If a server isn't configured to send the correct headers with the SVG files it serves, then a browser like Mozilla won't treat those files as SVG. Instead it will most likely show the markup of the files as text or encoded garbage, or even ask the viewer to choose an application to open them. For normal SVG files, servers should send the HTTP header:
Content-Type: image/svg+xml
For gzipped SVG files, servers should send the HTTP headers:
Content-Type: image/svg+xml Content-Encoding: gzip
You can check that your server is sending the correct HTTP headers with your SVG files by using a site such as web-sniffer.net. Submit the URL of one of your SVG files and look at the HTTP response headers. If you find that your server is not sending the headers with the values given above, then you should contact your Web host. If you have problems persuading them to correctly configure their servers for SVG, there may be ways to send the correct HTTP headers yourself. How you do this will depend on the server your SVG is hosted on, or on the technologies it provides. Choose from one of the servers/technologies listed below.
