KML/KMZ URL in Placemark Description Fails?

[foatus]

I'm trying to develop a placemark which contains KML URLs which when clicked will result in additional KML being loaded into GE. I have a KML file with the following description element:

<description>&lt;a href="http://radon/ge/6325.kml"&gt;6325&lt;/a&gt;</description>

When I click on this link in GE I get the following error dialog:

"Fetch of http://radon/ge/1739.kml failed: Http: Not Acceptable"

Other observations:

1) I get the same result with "Show web results in external browser" on or off.

2) When I cut and paste the URL from the description popup into IE it loads the KML file into GE as expected.

3) I get same error with KMZ and KML URLs.

So it seems like GE is disallowing URLs with KML/KMZ extensions. Any ideas out there on what's happening?

Thanks,
Bill

[PenguinOpus]

Older versions of the beta had this problem, but .0616 should be able to do this for both kml and kmz.

[TJ1]

I've just suffered this, too!

Loading a static KML from an IIS 6 web server directly into GE (from a NetworkLink), IIS returns HTTP 406 Not Acceptable to Google Earth because the mime-types that GE sends in its Accepts: Request aren't matched to the Mime-Types that IIS is prepared to deliver.

This appears to be a problem with IIS getting confused about its registered Mime-Types either in the server-wide Mime-types settings, or the ones covering the individual sites or even directories.

The same download works when tried from a 'proper' browser such as IE or Firefox.

When I saw this I ran Ethereal on the client and snooped the conversation between GE and IIS.

Everything looked okay but IIS was logging 406 consistently on all virtual hosts so I deleted the Mime-Type mapping for KML, and tried again.

This time IIS reported 404 Not Found.

I then added the Mime-Type (.kml="application/vnd.google-earth.kml+xml") back in and tried again, and it worked.

I hope this helps someone else in the future because its an obscure bug to track down. I just wish I could work out why GE failed but other browsers didn't.

TJ.

------ 406 Not Acceptable --------------

Hypertext Transfer Protocol
GET /play/test.kml HTTP/1.1\r\n
Request Method: GET
Request URI: /play/test.kml
Request Version: HTTP/1.1
Accept: text/plain, text/html, text/xml, text/xml-external-parsed-entity, application/octet-stream, application/vnd.google-earth.kml+xml, application/vnd.google-earth.kmz, image/*\r\n
Cache-Control: no-cache\r\n
User-Agent: kh_lt/LT3.0.0616\r\n
Host: lan.tjworld.net\r\n
Connection: Keep-Alive\r\n
\r\n

Hypertext Transfer Protocol
HTTP/1.1 406 Not Acceptable\r\n
Request Version: HTTP/1.1
Response Code: 406
Content-Length: 1713\r\n
Content-Type: text/html\r\n
Server: Microsoft-IIS/6.0\r\n
X-Powered-By: TJ's Whacky Ideas\r\n
PICS-Label: (PICS-1.0 "http://www.rsac.org/ratingsv01.html" l by "webm...@tjworld.net" on "2005.10.13T12:53+0100" exp "2006.12.31T12:00+0100" r (v 0 s 0 n 0 l 0))\r\n
Date: Wed, 19 Oct 2005 01:38:29 GMT\r\n
\r\n

------- 404 Not Found ----------------

Hypertext Transfer Protocol
GET /play/test.kml HTTP/1.1\r\n
Request Method: GET
Request URI: /play/test.kml
Request Version: HTTP/1.1
Accept: text/plain, text/html, text/xml, text/xml-external-parsed-entity, application/octet-stream, application/vnd.google-earth.kml+xml, application/vnd.google-earth.kmz, image/*\r\n
Cache-Control: no-cache\r\n
User-Agent: kh_lt/LT3.0.0616\r\n
Host: lan.tjworld.net\r\n
Connection: Keep-Alive\r\n
\r\n

Hypertext Transfer Protocol
HTTP/1.1 404 Not Found\r\n
Request Version: HTTP/1.1
Response Code: 404
Cache-Control: max-age=60\r\n
Content-Length: 1635\r\n
Content-Type: text/html\r\n
Server: Microsoft-IIS/6.0\r\n
X-Powered-By: TJ's Whacky Ideas\r\n
PICS-Label: (PICS-1.0 "http://www.rsac.org/ratingsv01.html" l by "webm...@tjworld.net" on "2005.10.13T12:53+0100" exp "2006.12.31T12:00+0100" r (v 0 s 0 n 0 l 0))\r\n
Date: Wed, 19 Oct 2005 01:42:50 GMT\r\n
\r\n

------ 200 OK --------------

Hypertext Transfer Protocol
GET /play/test.kml HTTP/1.1\r\n
Request Method: GET
Request URI: /play/test.kml
Request Version: HTTP/1.1
Accept: text/plain, text/html, text/xml, text/xml-external-parsed-entity, application/octet-stream, application/vnd.google-earth.kml+xml, application/vnd.google-earth.kmz, image/*\r\n
Cache-Control: no-cache\r\n
User-Agent: kh_lt/LT3.0.0616\r\n
Host: lan.tjworld.net\r\n
Connection: Keep-Alive\r\n
\r\n

Hypertext Transfer Protocol
HTTP/1.1 200 OK\r\n
Request Version: HTTP/1.1
Response Code: 200
Cache-Control: max-age=60\r\n
Content-Length: 933\r\n
Content-Type: application/vnd.google-earth.kml+xml\r\n
Last-Modified: Wed, 19 Oct 2005 01:11:47 GMT\r\n
Accept-Ranges: bytes\r\n
ETag: "adf713144ad4c51:394"\r\n
Server: Microsoft-IIS/6.0\r\n
X-Powered-By: TJ's Whacky Ideas\r\n
PICS-Label: (PICS-1.0 "http://www.rsac.org/ratingsv01.html" l by "webm...@tjworld.net" on "2005.10.13T12:53+0100" exp "2006.12.31T12:00+0100" r (v 0 s 0 n 0 l 0))\r\n
Date: Wed, 19 Oct 2005 01:44:25 GMT\r\n
\r\n

[foatus]

I know this response is a little late, but upgrading did fix the problem.

Thanks,
Bill

[foatus]

Ugh. This problem will not go away...

I'm now experiencing something very similar to what TJ describes in this thread, although I'm not having any success resolving the problem..

Bottom line is I'm trying to serve out KMZ form IIS using links within GE placemark descriptions fields. I've configured the MIME type on IIS. I can copy the link out of the description, paste it into a mainstream browser and download the KMZ. When I attempt to load the KMZ using the placemark description link I get a "HTTP: Not Acceptable" error (406) in GE. I've used Ethereal to looks at the headers, and it looks like the GET issued by GE is specifying the same MIME type I've entered into IIS - 'application/vnd.google-earth.kmz kmz.'

IIS - version 6.0
GE - 3.0.0762

Any help appreciated...

Bill

[hyoung]

I had the same problem til a minute ago with 4.0.1693 (beta) and iis 5.1 on XP (I havent tried it on iis 6 yet).

After reading the posts here (thanks, was usual info), i decided it may be that i defined the type twice as the problem (server wide and in the application directory). by removing the server wide definitions it started working as expected with a static kml file.

Hopefully it will stay working.

create a virtual directory(s) and add the mime types there not server wide and see if it solves your problem.

- Hope this helps,
- Henry .'.