Now I've checked and rechecked my system this is what I pass the UDP:
AUTH user=han&pass=solo&protover=2&client=kinglink&clientver=1
this is NOT my username not my password, and not anything.
Now I can do user k, pass k, user l pass l, and random letters as long as they are lowercase. It ALWAYS gives me a 200.
So let's step up to the next problem. Who am I logged in as? I can't tell you for sure but I do a NOTIFYLIST with the NEW session id it returns my personal info, however I'm not han, my password is not solo. I'm kinglink.
Now i've just messed around with my UDP port tester. it appears I never sent a Logout and after logging out I get 500 Login failed when trying this line. So obviously it's now REQUIRED to logout? But to do that you must LOGOUT with the session key. If you don't it appears that if you have the same IP and the same UDP port (I use 9000) and you try to login with out the last code being logged out you immediatly get logged into the old sesson and it looks like it's a new session. Now again there's no way to test who you are in the program.
However let's think about this? Let's assume computer shuts down, program crashes, or something. We have to assume you don't always log out (yes if you close the program you log out but I personally never log out of some programs, and as I code a notification program this program should NEVER need to be closed until shut down so we have to assume that if anything happens to the puter then the connection gets servered.
My question comes down to this. If I don't have a session id, the only way I can think of making sure no one is falsely logging in is to log in on my side with this problem is that I login, if I get a 200, I log out, and then log back in, if I get a second 200, then I assume I'm clear. The other option is to login as a impossible name (I'll have to use either a given name and password you give me or "kinglink/kinglink" a l/p I'll never use. and see if I get 200. If I do I immediatly log out and login normally.
Both options seem needlessly complicated, and useless, the later has the least error checking, but is there anyway around this problem with out having to issue two commands, such as a universal logout command to make sure you're starting a new session?
Any other developer find this out or am I the first time find a glitch? if so I want to name it the "kinglink false entry"
