GeoNames Forum

Hi,

I'm having a problem accessing the countrycode service from Flash when run in IE6. I haven't found a fix yet, but I did see that the security policy file (/crossdomain.xml) as deployed on both geonames.org and geonames.web are outdated.
Since Flash player 9 the format of this file has been changed. The "simple" version that allows acces to anyone is like this:

<?xml version="1.0"?>
<!DOCTYPE cross-domain-policy SYSTEM "http://www.macromedia.com/xml/dtds/cross-domain-policy.dtd">
<cross-domain-policy>
<allow-access-from domain="*" />
<site-control permitted-cross-domain-policies="master-only" />
</cross-domain-policy>

Note 2 changes:
- addition of node <site-control>
- no attribute 'secure="true"' in node <allow-access-from>

Can you change the crossdomain.xml on both locations to the updated version? I'm not sure this will fix my problem, but at least your server will be more compliant with the current state of affairs in flash-land.

Thanks!

Hi Stephan

I have modified the file. Hope it is fine for you and it does not break any existing application.

Marc

Hi Marc,

Thanks for the fast update!

Unfortunately this didn't solve the specific problem, so we'll have to resort to using a proxy. If I ever find the culprit I'll post my findings here.

Cheers,

And back with more info on this as promised. The error I'm getting is #2032, which is Flash's garbage bin error code for when it can't deal with the situation of loading a file anymore. A long list of possible causes can be found in this blog post and comments:
http://www.judahfrangipane.com/blog/?p=87

About halfway through that page, someone mentions a situation with IE6 and certain headers being sent by the server:

response.setHeader(”Pragma”,”no-cache”); //HTTP 1.0
response.setHeader(”Cache-Control”,”no-cache”); //HTTP 1.1
response.setDateHeader (”Expires”, 0); //prevents caching at the proxy server

It seems that IE6 does not like the XML context type served up with these headers

These headers are indeed present in the responses from GeoNames. And it's not just XML, also the regular HTML-reponse breaks on this.

Now I suppose those headers are there for a good reason, and I can fully appreciate it if you're not willing to remove them. I guess it's quite likely that it would break someone's code out there if you did. We'll work around this with a proxy on our own server.

Cheers,

Thanks a lot for the update, Stephan. I don't dare changing it right now as it could cause problems to other users if we change it right now, but we will keep it in mind and possible do some changes later.

Best

Marc