Log in

No account? Create an account
LiveJournal Client Discussions [entries|archive|friends|userinfo]
LiveJournal Client Discussions

[ userinfo | livejournal userinfo ]
[ archive | journal archive ]

[Jun. 2nd, 2006|03:44 am]
LiveJournal Client Discussions


Hi, i have application which recursively receives friends lists from /misc/fdata.bml?user=... and i wish to make it use compressed data transfer mode but in vain.

Here is my request, it works with other sites and several parts of LJ itself.

GET %s HTTP/1.1\r\n
Host: %s\r\n
User-Agent: Bot 0.1\r\n
Accept: text/plain\r\n
Accept-Encoding: gzip, deflate\r\n
Connection: Close\r\n

Does somebody know what is the reason it doesn't work with fdata.bml?

[User Picture]From: hythloday
2006-06-02 12:56 pm (UTC)
You can't make a server transmit a resource compressed - you can only specify the compression algorithms you're willing to receive and let the server decide.
(Reply) (Thread)
[User Picture]From: fukanchik
2006-06-02 01:05 pm (UTC)
I know.
(Reply) (Parent) (Thread)
From: hattifattener
2006-06-06 06:01 am (UTC)
The LJ server might be more willing to provide a transfer-encoding than a content-encoding (see RFC2616 §14.39, §14.41, etc.; transfer-encodings are an HTTP/1.1 addition).

You can have gzip or deflate in either a content- or a transfer-encoding, but the meaning is slightly different. A content-encoding of gzip means that the server is sending you a compressed file — for example, if you retrieve an .svgz file, you might get an SVG content-type and a gzip content-encoding. A transfer-encoding, on the other hand, says that the server is sending you a regular old uncompressed file, but that it's being compressed for transport.

Does LJ's webserver support any of this? I have no idea.
(Reply) (Thread)
[User Picture]From: fukanchik
2006-06-06 12:06 pm (UTC)
Transfer-Encoding is indicator of tranformation which is applied to message body. I need reverse effect.
(Reply) (Parent) (Thread)