bmp
On Jan 11, 3:31 pm, jase wrote:
> Hello,
>
> I posted a message previously, but it seems inaccessible at this
> point.
>
> We're currently receiving a 403 Forbidden error when performing
> geocoding over https. I noticed that the url parameter of the
> geocoding
Hello,
I posted a message previously, but it seems inaccessible at this
point.
We're currently receiving a 403 Forbidden error when performing
geocoding over https. I noticed that the url parameter of the
geocoding call is using HTTP instead of HTTPS. I thought this was
fixed in 1_9a. Can anyone
I'm not sure when this started, but I'm using 1_9a, and Geocoding and
Directions were working fine over https a few months ago. They're no
longer working anymore. Is anyone else experiencing this problem?
Thanks,
--
You received this message because you are subscribed to the Google Groups
"Googl
Hello,
I recently ran into an issue this week where I was loading a swf
hosted on mapapp.host.com, into my main application which is hosted at
mainapp.host.com. The problem is that the outgoing calls to the google
maps api are passing a parameter named "url" which has the url of the
swf making th
has anyone tried loading directions over SSL?
On Jun 12, 1:57 pm, rockhowse wrote:
> flexible_dveloper is correct. After finding out that I needed to use
> 1.9a on https sites, I ran into the exact same issue you are
> reporting. in order to get it to work with flex modules I had to place
> it i
Hello everybody,
I'm working on a flex application that we are planning to server over
HTTPS, and I've gotten the maps to finally load after creating a
google maps keys with https:// as the prefix, and including
Security.allowInsecureDomain("maps.googleapis.com");
The problem is, the Directions.
