Sporadically Invalid XML in API-Replies (Surplus XML Declarations)

[Jan Krämer]

Hi,

I have been noticing that since this morning once in a while the replies
to calls to the API are looking like this:

http://twitter.com/statuses/user_timeline/???????.xml
----8><---------8><---------8><---------8><---------8><-----
<?xml version="1.0" encoding="UTF-8"?>
<statuses type="array">
<?xml version="1.0" encoding="UTF-8"?>
<status>
<created_at>Wed Mar 19 05:39:14 +0000 2008</created_at>
<id>XXXXXX</id>
<text>SDGFSDFGSD</text>
<source>web</source>
<truncated>false</truncated>
<in_reply_to_status_id></in_reply_to_status_id>
<in_reply_to_user_id></in_reply_to_user_id>
<favorited>false</favorited>
<user>
<id>12345</id>
<name>sdfgsdfg</name>
<screen_name>sdfsdfg</screen_name>
<location></location>
<description>sdfgsdfg.</description>

<profile_image_url>http://static.twitter.com/images/default_profile_normal.png</profile_image_url>
<url>http://www.sgdfgsdfg.com</url>
<protected>false</protected>
<followers_count>7</followers_count>
</user>
</status>
</statuses>
----8><---------8><---------8><---------8><---------8><-----

Clearly there is one xml declaration to many, or?

After some time (probably when the cache resets) it shows up normally
again. Also: there is a difference between calling the api with the id
or the name. (Do you cache those differently?)

I just wanted to let you know ;-)

Have a nice day

- Jan

[Alex Payne]

This is a known issue, and we're looking into it. Thanks for the report!

--
Alex Payne
http://twitter.com/al3x

[kurtisnelson]

This issue is now popping up for me in my API calls. It completely
breaks my application.

[Alex Payne]

We're going to be rolling back the change that caused this issue presently.

--
Alex Payne
http://twitter.com/al3x

[Jo Booth - Mesh|net]

Yeah I had that issue too:

<http://twitter.com/JoMangee/statuses/849665722>
goes 2 make the xml from http://twitter.com/favourit... into better
xml. XML header with every block? /me wonders about it. I'm L:comms
11:43 AM July 04, 2008 from web
Jo -mangee- Booth

[Evan Weaver]

Has this issue re-appeared at all, or have you noticed any other
unusual API issues? We're doing some a/b testing of a caching system
today and through the weekend.

Evan

--
Evan Weaver

[Jan Krämer]

Am Saturday, 5. July 2008 schrieb Evan Weaver:
> Has this issue re-appeared at all, or have you noticed any other
> unusual API issues?

No, that issue did not reappear, and the api has been runnig rather
smoothly for me. (Cannot decide if it is because of the long 4th of
July weekend in the US, or because of the upgrade you guys did; but I
would imagine the latter helped a lot, so thank you :-)

One rather unusual issue, which I have seen exactly once today and I
observed only by chance (but, since you asked...), is the following:

----8><---------8><---------8><---------8><---------8><-----

<statuses type="array">
<status>
<created_at>Sat May 24 12:30:22 +0000 2008</created_at>
<id>[SOME_ID]</id>
<text>[SOME_TEXT]</text>

<source>web</source>
<truncated>false</truncated>
<in_reply_to_status_id></in_reply_to_status_id>
<in_reply_to_user_id></in_reply_to_user_id>

<favorited></favorited>
<user>
<created_at>Thu Jul 03 20:38:31 +0000 2008</created_at>
<id>[SOME_OTHER_ID]</id>
<text>[SOME_OTHER_TEXT]</text>

<source>web</source>
<truncated>false</truncated>

<in_reply_to_status_id>[AND_ANOTHER_ID]</in_reply_to_status_id>
<in_reply_to_user_id>[TOTALLY_OTHER_ID<]/in_reply_to_user_id>
<favorited></favorited>
</user>
</status>
[..snip..]

</statuses>
----8><---------8><---------8><---------8><---------8><-----

(I masked most info, but I guess the problem is clear. It occured around
16:10 Central European Summer Time, so about 8:10 am PST?)

As I said, the API runs very well and very responsive for me, but that
reply was so weird I just had to report it. ;-)

Have a nice Day

- Jan Krämer

[Evan Weaver]

Thanks. That's real weird. Can you email me off-list the exact details
of that error?

Evan

--
Evan Weaver