HAO choking on an empty extent

[joe]

I noticed the following showing up in the error logs:

vso_strict : Query Result $VAR1 = [
          {
            'provider' => 'HAO',
            'version' => '0.6',
            'error' => '404 Bad Request - Invalid EXTENT'
          }
        ];

Which is to say the MLSO provider isn't happy with the 'extent' from something. (I noticed a couple go by ~4pm)

[joe]

in the MLSO proxy, I had made a few adjustments in what gets sent to HAO (to deal with outdated code on their system ... see #13 )-- such as stripping out 'null' elements.

Unfortunately, when the IDL client sends no extent type, all items in extent get stripped, but not the extent complexType. I've now got it removing those, too, so it's at least going back to 'acceptable' behavior (which is at least running the query, but I still get frequent timeouts)

[joe]

no wonder I was timing out ... I asked for a _year_ of data, not a day. oops. I'm getting returns just fine now.

oh ... and it was Bill Thompson, it turns out, who triggered the error.