Google Earth’s Issue logging …

Where is it?
I have had many queries regarding their HTTPS support of network links and image overlays but these always seem to land on deaf ears or gets lost amongst the thousands of arguably useless posts on the community forum.

Makes you realise how refreshing it is when projects have public JIRA/Bugzilla interfaces available so you can at least give feedback
From the release notes of the latest BETA 4 (4.0.1657) via GEBlog, the offcial word,

Reporting Errors
----------------

To report an error, you should first consult the Google Earth Help Center and
the Google Earth Community. They are both excellent sources of information.

Well my issue isn’t resolved in any of these resources and I’m kinda resorting to the blogosphere in a last ditched effort so someone may see it,

Problem: GE does some very weird handling of any network link or image/screen/ground overlay that is being sourced over HTTPS (as distinct from HTTP). I would imagine most would not even notice this, but as a few of my WMS services exclusively use HTTPS i stumbled upon the following problems,
GE v3 (current stable): If a groundoverlay href containts a HTTPS link with a query string, Google Earth strips out the query string when making the request to the remote URL. In my WMS case, this would mean the HREF would contain

https://my.wms.server.com/wms?Service=wms&Version=1.1.1&Request=Getmap….

but then GE would actually only request

https://my.wms.server.com/wms

which results in no image being returned.

GE v4 (any beta vers): I was hoping v4 may have fixed the HTTPS problem but it appears they have made it even stranger. Now if i request a WMS groundoverlay via HTTPS, GE interprets the https:// path as a relative link to the KML host address so if i’m sourcing the network link from http://my.networklink.com/link.kml … the address requested by GE would actually be

http://my.networklink.com/https:/my.wms.server.com/wms ….

What the ~!?

Since GE uses the libcurl.dll libraries, HTTPS support should be a given. I’m sure its a very small configuration change that’s required but its extremely frustrating!

In other good news, i’m pretty eager to see when wmsbase.dll is linked into the binary. From what i can gleam from the code, it’s containing proper WMS 1.1.1 GetCapabilities parsing which is propably what James Macgill has been working on. I better get my skates on releasing my own similar code!