Hi Milan,
This is the problem preventing us from using gzip/deflate in
issue 154 (http://code.google.com/p/twitter-api/issues/detail?id=154).
This is a problem with one of the libraries our public_timeline code
is using. We're looking at replacements currently since this same
library has caused us trouble before.
Thanks;
— Matt Sanford (@mzsanford)
On Dec 7, 2008, at 06:45 PM, Milan Cermak wrote:
When requesting the public_timeline, the server adds a "Content-
Encoding: UTF-8" header:
$ curl --head http://twitter.com/statuses/public_timeline.xml
HTTP/1.1 200 OK
Date: Mon, 08 Dec 2008 02:36:31 GMT
Server: hi
Content-Encoding: UTF-8
Content-Type: application/xml
Content-Length: 18027
Set-Cookie: JSESSIONID=65D7E5CCAAEDC24F18665B43EECF27B9; Path=/
Cache-Control: max-age=1800
Expires: Mon, 08 Dec 2008 03:06:32 GMT
Connection: close
This is not according to the RFC (Content-Encoding header:
http://tools.ietf.org/html/rfc2616#section-14.11 content codings:
http://tools.ietf.org/html/rfc2616#section-3.5).
Requests to other files are OK, e.g.:
$ curl --head http://twitter.com/statuses/show/1000323.xml
HTTP/1.1 200 OK
Date: Mon, 08 Dec 2008 02:36:09 GMT
Server: hi
Last-Modified: Mon, 08 Dec 2008 02:36:09 GMT
Status: 200 OK
ETag: "cdccfd306aac8c9bd5928c03ef13b70f"
Pragma: no-cache
Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post-
check=0
Content-Type: application/xml; charset=utf-8
Content-Length: 838
Expires: Tue, 31 Mar 1981 05:00:00 GMT
Set-Cookie:
_twitter_sess
=
BAh7CToJdXNlcjA6DnJldHVybl90byIxaHR0cDovL3R3aXR0ZXIuY29tL3N0
%250AYXR1c2VzL3Nob3cvMTAwMDMyMy54bWw6B2lkIiUyYzhhNjBkMDJlMzFjYjdm
%250ANjc4M2UzZjFhYmU1NTM1NyIKZmxhc2hJQzonQWN0aW9uQ29udHJvbGxlcjo6
%250ARmxhc2g6OkZsYXNoSGFzaHsABjoKQHVzZWR7AA
%253D%253D--52a70e55dbef337e8e8ca986260e65299a4a151f;
domain=.twitter.com; path=/
Vary: Accept-Encoding
Connection: close
I know it's just a minor annoyance but could it be fixed? Thanks,
Milan
