Network link and MIME types

[horizon]

According to the tutorial a network link must return either text/plain or application/keyhole as MIME type. I tried a network link with MIME type application/vnd.google-earth.kml+xml and extension KML, but that gives the error "http: not acceptable". Why doesn't that work too, as regular kml files on a server must also return that same MIME type?

[horizon]

It seems that it does work when the HTTP response charset is set to UTF-8.

[PedroMCi]

Does anyone know how to work arround this problem?
I´ve got a web space given my ISP, and tried to host the files on my area, but it always throughs the Not Acceptable error. Can't ask the isp to change the settings, is there another way to change this?

[PedroMCi]

Ok, I've found something.
I´ve put a tcp tracer between GE and my web server (IIS 5.1). I could see that the GE application accepted a lot of formats, but it didn't accepted the 2 mime types defined by Google. So IIIS, always respondend "Not Accepted".
I went into the IIS mime types configuration and changed the .kml mime to text/xml. Since this was one of the format the GE app accepted, IIS would send it correctly and my Network link started to work. This is a funny workarround, but 'till they come up with a diferent version of GE, it works.

[pseabury]

I had a problem similar to this recently. It seems that kml network links (links that try and retrieve kml that is) work fine with the MIME type set to text/plain. However, if your network link tries to pull a kmz, then you need to get a server response with the proper GE MIME type. You also have to write the kml (even if it's zipped) with utf-8 and not us-ascii encoding.

I simply wrote a service order to my Domain host and they added the proper MIME types to my server within a day.

Paul

[bob_wenzlau]

I stumbled into this post trying to deploy Region-based NetworkLinks. I was getting http: refusal from an IIS environment in the child folders (not the root folder).

The 2.0 tutorial indicated Google Earth reads KML and KMZ files, and the MIME types for these are:
* application/vnd.google-earth.kml+xml kml
* application/vnd.google-earth.kmz kmz

This ended up with the stated http: refusal within network links. I followed the direction in this post to change the kml mime to text/plain -- With this change the network link child folders worked! This solved the network link problem, but generated a new problem. Now when you refer a person to the link, using a kml extension, rather that starting GE, it just reveals the XML in the browser as text. The user would be flustered.

So my work around is to refer the user via a kmz link which still will invoke Google Earth, and then allow the mime to be in a text/xml format which will allow the network links to work.

While this was an old post, the issue still seemed relevant. this was my progress on the issue.