Log in

No account? Create an account
hmmm. - LiveJournal Client Discussions — LiveJournal [entries|archive|friends|userinfo]
LiveJournal Client Discussions

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

hmmm. [Mar. 22nd, 2002|11:51 am]
LiveJournal Client Discussions



Out of curiosity to the other LJ Client developers out there;

When you are composing your HTTP form to be posted to the server, for a "postevent", do all of you set all of the variables first, then have the "event" data at the end?

I was just looking at some docs, and it seems that some form posting mechanisms cut off a post after a certain number of bytes. I haven't yet tested the LJ servers to see if this is the case here, but if there was a situation where a journal user was posting a very long entry that they wanted to be private, but it ended up being so long that the resulting HTTP form got truncated, and the client put the "security=private" at the end, then that 'security' flag would be lost, making the post "public" instead.

Has anyone experimented with this? Do the other clients put the flags before the body? Or, conversely, do the LJ servers accept forms of unlimited size?


[User Picture]From: avva
2002-03-22 09:20 am (UTC)
LJ servers certainly accept forms long enough to hold the maximum possible size for an entry (and other relevant information).

Right now entries that are too long are just silently truncated, but very soon (it's on my soon-to-fix bug list) they will be rejected with an error. So it won't (and probably already doesn't) matter in what order you assemble the form.
(Reply) (Thread)
[User Picture]From: jerronimo
2002-03-22 10:26 am (UTC)
Excellent. Thanks!
(Reply) (Parent) (Thread)
[User Picture]From: wolfieboy
2002-03-22 09:24 am (UTC)
I haven't looked recently but I'm assuming that LJ will accept using POST for a postevent as opposed to a GET. GET can easily be cut off - I've found the limit to be between 250-1000 characters. POST on the other hand has no limit on the size of your post data.
(Reply) (Thread)
[User Picture]From: sapphirecat
2002-03-22 05:05 pm (UTC)


Some firewall or proxy software might cut off POST data at a certain number of bytes. But in that case, the Content-length header would mismatch, so it'd still be detected as an error at LJ, right?

My client just iterates over a hash (Perl), so I have no clue what order the fields are sent in. It's not guaranteed anyway.
(Reply) (Thread)