fub in lj_dev

Flat protocol broken?

Mar 16, 2010 21:23

I've just discovered that I can't get any challenges anymore in my LJ client. I get an error response saying that I did not specify a mode. But until ten minutes ago, everything was working fine...

Telnet session in here )

client, *report (lj), client: authentication, client: flat, bugs: client protocol, *fixed, bugs, client: sessions

Leave a comment

Comments 40

pauamma March 17 2010, 01:11:15 UTC
No answer for you (I may codedive tomorrow if I have the time), but it's not just you - I had 2 other entries asking the same in the moderation queue, and I steered them toward commenting on yours instead to avoid splitting info.

ETA: timing makes it very likely it's related to the latest LJ code release.

Reply

azurelunatic March 17 2010, 01:15:29 UTC
There's discussion about there having been problems with clients around the time of the release.

It may or may not still be going on.

Release notes here: http://community.livejournal.com/lj_releases/55347.html

Reply

pauamma March 17 2010, 01:34:16 UTC
Yeah - I just read that, and I saw no mention except for a general brokenness report (asked them to compare their symptoms to this, just to make sure).

Reply


agent_mimi March 17 2010, 01:25:12 UTC
When I try to auto login, I get an error box that says "Client error: No mode specified". Several people have mentioned the same thing today in comments to this old post:

http://community.livejournal.com/lj_dev/388904.html

Reply

pauamma March 17 2010, 01:37:34 UTC
Still happening now? (Just in case this was turbulence while the release was happening.)

Reply

allah_sulu March 17 2010, 02:01:04 UTC
Still happening. Client error: no mode specified.

Reply

pauamma March 17 2010, 02:09:06 UTC
Thanks.

Reply


raven_ap_morgan March 17 2010, 01:41:20 UTC
MultiLJ is working, and it uses the flat protocol. I noticed in the Telnet session that the mode was not the first variable in the list - I always issue mode first, so I wonder if that has something to do with it. Also, getchallenge uses no additional variables - ver is not required in that call.

Just some thoughts...

Reply

allah_sulu March 17 2010, 02:01:28 UTC
I tried putting the mode in a different place in the list, and it didn't help.

Reply

pauamma March 17 2010, 02:10:49 UTC
Can you try removing ver= (if it is present in your code) to see if it changes things?

Reply

allah_sulu March 17 2010, 02:13:08 UTC
It's not in my code.

Reply


crustycurmudgeo March 17 2010, 02:15:55 UTC
This showed up earlier with DeepestSender.

I deleted all my livejournal cookies then relogged in and all was fine.

Reply

allah_sulu March 17 2010, 10:20:16 UTC
I just deleted my entire cache, cookies and all, and it's still not working for me.

Reply

fub March 17 2010, 10:28:17 UTC
When I tried it this morning (4.5 hours ago) it was working for my client...
You can try it out with a telnet client -- send the request as above, and see what you get back. If you get the error (again), it's not in your/the code and it's (still) broken (again) at the LJ end.

Reply


arethinn March 17 2010, 07:09:06 UTC
I've seen people complaining that this "broke Semagic" but I was able to log in and post OK just now without changing anything.

Reply

pauamma March 17 2010, 14:24:31 UTC
Thanks for the report. Might have been fixed meanwhile - http://community.livejournal.com/changelog/8248335.html.

Reply


Leave a comment

Up