loke@sleipner:~$ ping -c 2 developer.garmin.com
PING developer.garmin.com (204.77.162.113) 56(84) bytes of data.
64 bytes from 204.77.162.113: icmp_req=1 ttl=240 time=166 ms
64 bytes from 204.77.162.113: icmp_req=2 ttl=240 time=161 ms
--- developer.garmin.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 5182ms
rtt min/avg/max/mdev = 161.828/164.028/166.228/2.200 ms
But the more complex communication from a web browser just times out. Don't know if I normally should get more hops from a traceroute, but here they are as a sort of data point for people with more knowledge [my first hop IP-number is X:ed out]:
loke@sleipner:~$ traceroute developer.garmin.com
traceroute to developer.garmin.com (204.77.162.113), 30 hops max, 60 byte packets
1 hxx-xx-xxx-x.dynamic.se.alltele.net (xx.xx.xxx.x) 6.638 ms 6.611 ms 6.596 ms
2 93.182.128.109 (93.182.128.109) 16.338 ms 16.347 ms 16.345 ms
3 h79-138-0-29.static.se.alltele.net (79.138.0.29) 16.166 ms 16.200 ms 16.200 ms
4 * * *
5 xe-9-1-2.edge3.Stockholm2.Level3.net (213.242.69.213) 28.830 ms 28.856 ms 28.847 ms
6 ae-1-51.edge3.NewYork2.Level3.net (4.69.138.196) 273.440 ms 253.252 ms 253.201 ms
7 ae-1-51.edge3.NewYork2.Level3.net (4.69.138.196) 253.189 ms 116.465 ms 116.434 ms
8 jfk-brdr-04.inet.qwest.net (63.146.26.5) 116.421 ms 116.425 ms 116.413 ms
9 * * *
10 67.135.58.206 (67.135.58.206) 162.872 ms 165.262 ms 165.250 ms
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
The plugin that you are using assumes that the resource is available via the secure url, and it is not. While it would be nice for Garmin to update their developer site to support https, it is not their fault that the plugin you are using makes such a bold assumption and doesn't fall back to the url that was provided. Additionally, the problem that you're seeing is listed in the FAQ as item #1, because they know it to be a problem with some sites.
