0

Does YQL support forced gzip results?

Hello,

I am trying to create an open table definition for StackOverflow and friends. I get the following error:
Unable to parse data using default charset utf-8

The full response and reproduction is at :
CODE
<?xml version="1.0" encoding="UTF-8"?>
<query xmlns:yahoo="http://www.yahooapis.com/v1/base.rng"
yahoo:count="0" yahoo:created="2010-08-13T02:15:07Z" yahoo:lang="en-US">
<diagnostics>
<publiclyCallable>true</publiclyCallable>
<url execution-time="1387" proxy="DEFAULT"><![CDATA[http://www.outerthoughts.com/files/opentables/se-stats.xml]]></url>
<url error="Unable to parse data using default charset utf-8"
execution-time="201" proxy="DEFAULT"><![CDATA[http://api.stackoverflow.com/1.0/stats?type=jsontext]]></url>
<user-time>1609</user-time>
<service-time>1588</service-time>
<build-version>8771</build-version>
</diagnostics>
<results/>
</query>


It seem to be consistently reproducible.

I have a full thread about this at StackApps (API part of Stack Overflow)

One of the suggestions is that (maybe?) API forces gzipped content back even if YQL does not support it (?). I tried checking it with ?debug=true flag, but it does not generate any additional info.

Could someone more familiar with YQL confirm or deny this path of investigation?

Thank you,
Alex.

by
0 Replies

Recent Posts

in YQL