API requests with an offset >= 1600 intermittently return HTTP error 400. about twitch-api HOT 4 CLOSED

I'll look into this. FWIW, we enforce a 100 limit - so you should probably
not set it so high :)

On Fri, May 11, 2012 at 12:41 PM, mike-rsi <
[email protected]

wrote:

I frequently receive HTTP error 400 responses from the API to what seem to
be well-formed HTTP requests sent through cURL. Every time I've checked
the API call manually by copying that exact API URL into a browser
(Firefox) immediately after having received the 400 response through cURL,
I get the expected data returned with an HTTP 200 response (i.e. I've never
seen the 400 response while testing the API in a browser).

In addition, I have only ever received the 400 response when the "offset"
GET parameter was set to 1600 or higher (e.g. 1700, etc.). When I start
seeing the 400 errors on these high-offset calls, it seems they happen for
hours at a time, although there will also be "good" (i.e. HTTP 200)
responses to the same high-offset calls mixed in during that time as well.
Then there will be hours (or days) at a time where I do not see a 400
response.

This is an example of the raw HTTP request header sent from cURL that
(sometimes) receives the 400 response:

GET /api/stream/list.json?category=gaming&limit=100&offset=1600 HTTP/1.1
Host: api.justin.tv
Accept: /
Accept-Encoding: gzip

---

Reply to this email directly or view it on GitHub:
https://github.com/justintv/twitchtvapi/issues/4

from twitch-api.

Thanks for looking into it. I do still adhere to a limit of 100. It's the offset that's high when the problem arises. So in the example I'm trying to retrieve the 100 records between 1600 and 1699. That should be okay, right? Thanks for the help!

from twitch-api.

Oh dude, yeah - that is fine. Sorry my brain transposed "limit" for some reason <_<.

Sent from my iPhone

On May 14, 2012, at 12:21 PM, [email protected] wrote:

Thanks for looking into it. I do still adhere to a limit of 100. It's the offset that's high when the problem arises. So in the example I'm trying to retrieve the 100 records between 1600 and 1699. That should be okay, right? Thanks for the help!

---

Reply to this email directly or view it on GitHub:
https://github.com/justintv/twitchtvapi/issues/4#issuecomment-5699497

from twitch-api.

This issue is reported fixed in the Twitch streams API.

from twitch-api.