Skip to main content

Tweak OpenLayers to get parse GetCapabilities working in IE

It happened to me recently that I needed OpenLayers (version 2.11) to parse a GetCapabilities response from Geoserver to present the user a list of layers to pick from.

The capabilites request is made through a Sproutcore request, which is basically a jQuery ajax object in disguise.
This of course works beautifully in every browser with the notable execption of ... IE (IE9 included).

The cause is that IE will helpfully xml-parse a response whose content-type is text/xml, but will refuse to parse a document whose content-type is application/vnd.ogc.request+xml. To add comedy to the drama the responseXML attribute of response is not null, as one would expect, but is instead set to reference an empty dom.

The workaround is to put a giant browser-sniffing if in your javascript to handle IE differently.
The code is like the following and please note that it is Sproutcore code, so browser sniffing and other amenities are peculiar to Sproutcore:

// God mess IE
if(SC.$.browser.msie) {
    content=response.responseText;
    var xmlDoc = new ActiveXObject("Microsoft.XMLDOM");
    // required or IE will attempt to validate against DTD, which could fail
    // because the dtd is not accessibile and we don't really care
    // we will notice later if any layer was loaded from the response anyway
    xmlDoc.async = false;
    xmlDoc.validateOnParse = false;
    xmlDoc.resolveExternals = false;
    var parsed=xmlDoc.loadXML(content);
    if(!parsed) {
        var myErr = xmlDoc.parseError;
        alert(myErr.reason);
    } else {
        content=xmlDoc;
    }
}

var wmsCapabilities = new OpenLayers.Format.WMSCapabilities();
var capabilities = wmsCapabilities.read(content);
// use the capabilities as you wish


IMPORTANT: remember to set the Proxy Base Url in the Geoserver Global configuration page to the correct value if using a reverse proxy.

Comments

Popular posts from this blog

Indexing Apache access logs with ELK (Elasticsearch+Logstash+Kibana)

Who said that grepping Apache logs has to be boring?

The truth is that, as Enteprise applications move to the browser too, Apache access logs are a gold mine, it does not matter what your role is: developer, support or sysadmin. If you are not mining them you are most likely missing out a ton of information and, probably, making the wrong decisions.
ELK (Elasticsearch, Logstash, Kibana) is a terrific, Open Source stack for visually analyzing Apache (or nginx) logs (but also any other timestamped data).

From 0 to ZFS replication in 5m with syncoid

The ZFS filesystem has many features that once you try them you can never go back. One of the lesser known is probably the support for replicating a zfs filesystem by sending the changes over the network with zfs send/receive.
Technically the filesystem changes don't even need to be sent over a network: you could as well dump them on a removable disk, then receive  from the same removable disk.

RUNDECK job maintenance

Learn more about Rundeck.

Now that I have a fair number of jobs scheduled by Rundeck, how do I periodically prune the job execution history and keep only the last, say, 30 executions for each job?