Status Update
Comments
ev...@gmail.com <ev...@gmail.com> #2
This is to confirm that we plan to resume the rollout of the new cross-signed root CA certificate as described in
The rollout will be very gradual, with incremental launches across the Google Maps Platform services and regions, and its phases will proceed depending on engineering evaluations rather than by a defined timetable. The change will be transparent to the vast majority of Google Maps Platform API clients, including all mainstream maintained OS versions.
For more information, please see the FAQ resources listed in
ev...@gmail.com <ev...@gmail.com> #3
At this stage, the best course of action is to ensure that your client TLS stack can dynamically work with intermediary certificates signed by any of the (~40) root CAs from
In other words, the root CA signing intermediary certificates for requests to
We have published FAQs at the following addresses:
zi...@google.com <zi...@google.com> #4
Here are several sources that can be used to help you split the root.pem file into 1 file per certificate, if required by your tooling and software environment:
-
-
-
As an immediate fix to get your Google Maps Platform requests working again, the main certificate to install is the "GTS Root R1" certificate, which begins at line 896 in the current roots.pem file. Please note that this issue may reoccur in the future if you don't install all the certificates.
2i...@gmail.com <2i...@gmail.com> #5
To help customers using Java or Mozilla NSS, we have updated the Java keytool
and NSS certutil
sections in our
br...@gmail.com <br...@gmail.com> #6
Dear developers, the new GTS Root R1 Cross certificates have now fully rolled out to all Google Maps Platform services.
ko...@gmail.com <ko...@gmail.com> #8
st...@gmail.com <st...@gmail.com> #9
ro...@gmail.com <ro...@gmail.com> #10
ca...@gmail.com <ca...@gmail.com> #11
oc...@gmail.com <oc...@gmail.com> #12
ka...@gmail.com <ka...@gmail.com> #13
I have faced the same problem
GET file://
at...@gmail.com <at...@gmail.com> #14
2i...@gmail.com <2i...@gmail.com> #15
"if there's a workaround?" i dont think so, we need to wait for a patch.
(sorry for my english)
ed...@gmail.com <ed...@gmail.com> #16
ed...@gmail.com <ed...@gmail.com> #17
"if there's a workaround?" i dont think so, we need to wait for a patch.
Well... there is some kind of workaround, but it's useful only if your local html doesn't need any other local file or has any kind of relative links.
You can force any relative link to a path using the html tag base. Adding this to the head will force the relative link from file://.../openhand_8_8.cur to html://.../openhand_8_8.cur, where it should be.
< base href="
My problem? I can't use this... as I use a custom marker (local png file), and if you change the relative path, you change it for all your relative links :(
So... I'll have to wait until they fix the path to that openhand_8_8.cur
2i...@gmail.com <2i...@gmail.com> #18
<base href="
ed...@gmail.com <ed...@gmail.com> #19
If any of you can use this workaround, then great :) but I'll wait for the official fix anyway.
2i...@gmail.com <2i...@gmail.com> #20
i'll do to, but it helps a lot during debug session not freezing the software. So thank you for sharing the info, it's very much appreciate.
[Deleted User] <[Deleted User]> #21
ha...@gmail.com <ha...@gmail.com> #22
2i...@gmail.com <2i...@gmail.com> #23
2i...@gmail.com <2i...@gmail.com> #24
ko...@gmail.com <ko...@gmail.com> #25
st...@google.com <st...@google.com> #26
Sorry once again to all you file:// users.
Description
We're generating local html file embeded on our app using google map v3 javascript API.
With IE 11 this cursor load with the bad protocol like that :
"file://
and not
"
(please see the picture attached)
That cause random freezes of 10/20 secondes when loading the page.
Best Regards.