296065 - GoDaddy Web Host does not support SVG MIME type

Status: RESOLVED INVALID

(Tech Evangelism Graveyard :: English US, defect)

Description

[Jeff Schiller]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050523 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050523 Firefox/1.0+

GoDaddy is one of the largest web hosts in the U.S.  I asked GoDaddy to support
the SVG MIME type in their web servers, but their response was:

"there has been no announcement about adding support for SVG MIME type or when
it may be added"

They use Apache web servers, so I followed the instructions at
http://wiki.mozilla.org/SVG:MIMEType to update the .htaccess file for my own
website.  However, GoDaddy should support MIME type "image/svg+xml" ubiquitously.


Reproducible: Always

Steps to Reproduce:
1. Attempt to view an SVG site on a GoDaddy website that does not have the above
modifications to the .htaccess file.
2.
3.

Actual Results:  
The SVG source is shown.

Expected Results:  
The SVG image should have been rendered by Mozilla (if it had received its
proper MIME type).

Comment 1

[Bob Clary [:bc] (inactive)]

Jeff, as much as I appreciate your position I think this is more of a tech
support issue between you and godaddy. The fact that you can use .htaccess means
this is not even a permanent issue with you.

-> INVALID.

Comment 2

[Jeff Schiller]

Bob, 

I had been exchanging some emails with Jonathan Watt regarding SVG on Mozilla
and when I mentioned this, he asked me to raise a bug here so Moz could help
push the issue.  I'm only doing what I was told ;)

Regards,
Jeff

Comment 3

[Bob Clary [:bc] (inactive)]

Jeff, no problem. If you could add Jonathan's email to the cc list, we can
discuss what should be done. 

Comment 4

[Jonathan Watt [:jwatt]]

Bob, I asked Jeff to file this bug because I was under the impression that TE
people are interested in getting ISPs to send the correct HTTP headers for SVG
since we require them. Indeed I closed bug 283620 as invalid (the same issue,
but for comcast), but got my knuckles rapped.