Comment 2 for bug 918388

I think the source of the problem is really that the server isn't setting a Content-Type at all, even with *.json is requested -- which puts the problem (and therefore, fix) on the server side.