lists.json API call ignoring the callback parameter as of the last few hours

[Tim Meadowcroft]

I've been happily pulling back a user's lists with a query like

  http://api.twitter.com/1/lists.json?callback=abc&screen_name=schmerg

but suddenly (sometime in the last 24 hours I suspect) this is returning pure json, not jsonp.. that is

  {"lists":[], "next_cursor":0, "previous_cursor":0, "next_cursor_str":"0", "previous_cursor_str":"0"}

rather than 

    abc({"lists":[], "next_cursor":0, "previous_cursor":0, "next_cursor_str":"0", "previous_cursor_str":"0"})

which if course breaks me loading it in a script tag.

Other calls seem to still be respecting the callback parameter... any idea what might have changed ??

--

Tim

[Harshad RJ]

I can confirm this with my app as well (tDash).

Harshad RJ
http://twitter.com/h__r__j

[Tim Meadowcroft]

Glad it's not just me then !

Here's an entire curl request with headers in case that gives any clues (eg if it's particular hosts behind a load balancer)

Cheers

--

Tim

 curl -v "http://api.twitter.com/1/lists.json?callback=abc&screen_name=schmerg"

* About to connect() to api.twitter.com port 80 (#0)

*   Trying 199.59.148.87... connected

* Connected to api.twitter.com (199.59.148.87) port 80 (#0)

> GET /1/lists.json?callback=abc&screen_name=schmerg HTTP/1.1

> User-Agent: curl/7.21.4 (i686-pc-linux-gnu) libcurl/7.21.4 GnuTLS/2.10.5 zlib/1.2.5

> Host: api.twitter.com

> Accept: */*

> 

< HTTP/1.1 200 OK

< Date: Fri, 01 Jul 2011 18:28:34 GMT

< Server: hi

< Status: 200 OK

< X-Transaction: 1309544914-75829-41020

< X-RateLimit-Limit: 150

< ETag: "aab4fa3d9f5ae979ad19a12fa7fcccb0"

< X-Frame-Options: SAMEORIGIN

< Last-Modified: Fri, 01 Jul 2011 18:28:34 GMT

< X-RateLimit-Remaining: 145

< X-Runtime: 0.01157

< X-Transaction-Mask: a6183ffa5f8ca943ff1b53b5644ef114a933ec98

< Content-Type: application/json; charset=utf-8

< Content-Length: 100

< Pragma: no-cache

< X-RateLimit-Class: api

< X-Revision: DEV

< Expires: Tue, 31 Mar 1981 05:00:00 GMT

< Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post-check=0

< X-MID: 3e1aeaa17e566ebc8a4c9b2ebcc4f1a1ebb20bbf

< X-RateLimit-Reset: 1309548219

< Set-Cookie: k=78.149.138.182.1309544914102224; path=/; expires=Fri, 08-Jul-11 18:28:34 GMT; domain=.twitter.com

< Set-Cookie: guest_id=v1%3A130954491410552515; domain=.twitter.com; path=/; expires=Mon, 01 Jul 2013 06:28:34 GMT

< Set-Cookie: _twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCLqc9eYwAToHaWQiJWU5Mjc3MmMzNjVlZTIw%250AYTkxMTZiMGI5NjBkNGIzMWNhIgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy%250AOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--fb869e5bba31f66f478b99dc38035752adff4eaa; domain=.twitter.com; path=/; HttpOnly

< Vary: Accept-Encoding

< Connection: close

< 

* Closing connection #0

[Taylor Singletary]

Thanks everyone, I'll report this to the team -- not quite sure what's happening.

Just to set expectations, I also don't have an ETA on a fix.

@episod - Taylor Singletary

--

Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk

[Tim Meadowcroft]

On Friday, July 1, 2011 7:54:00 PM UTC+1, Taylor Singletary wrote:

Thanks everyone, I'll report this to the team -- not quite sure what's happening.

Just to set expectations, I also don't have an ETA on a fix.

Thanks - ETA not required, just one of things where filing a bug report is too heavywight ("add it to the prioritised list") but blind whinging feels like.. blind whinging.

Happy to hear it's been escalated for someone to at least have a look at whether it was intended or not, and it's not just me being an idiot (again).

Cheers

--

Tim

[Harshad RJ]

Hi Taylor,

Any updates on this issue?

tDash users are not able to read their lists because of this.

thanks,
Harshad

[Taylor Singletary]

Hi Harshad,

We hope to have a fix for this bug out next week, sorry for the inconvenience in the meantime.

@episod - Taylor Singletary

[Matt Harris]

Hey Tim, 

This should now be fixed. Let us know if you find it isn't.

Best,
@themattharris
Twitter

[Tim Meadowcroft]

On Thursday, July 7, 2011 12:45:05 AM UTC+1, themattharris wrote:

This should now be fixed. Let us know if you find it isn't.

Yep - confirmed as fixed for me ... many thanks guys !

--

T