Hey this project seems cool! I'm working on a similar project but for windows + mac + android!
Glad to see there's a linux awesome project so that area's covered I just just focus on those three.
I'm having a little issue when I login for mine though. I notice I login through the same url as well, but after successfully logging in I get an error. However I'm feeling like I can mostly ignore it, just so long as its working to log in... But it's kind of annoying and I'd like to get to the bottom of it!
For now to give an update on the app, things are coming along pretty nicely.
TLS is working and I just got it to log in successfully and pass me a valid session id cookie
You can tell when you're logged in as your password hash shows up in the rtmp info (is one obvious way anyway among others).
However there's an issue, where I get an 403 forbidden error after posting the data for some reason, but it still worked and it successfully logs in. Is this really an error or what is up with that? If I make handle redirects to false, I get a differnent not quite error, 302 found. and it still successfully logs in... Maybe it's better to stop at 302 found then with another instance of the class that has handle redirects enabled continue from there... As it seems handling redirects is neccessary to not to held up, and for things to work!
Successfully logged in with data relevant to being a logged in user rather than just anonymous
but that's after this:
I'm going to suppress the errors for sure, but 403 forbidden doesnt seem like something I want to be getting even if it successfully logs in! At least its working though
But thanks to anyone who can help me get rid of this error!
I know you get csrf token from cookies/hidden field on web page and then you have to post it to the login page as "csrfmiddlewaretoken" along with "username" and "password"... That's simple enough right? Finally you can add at the end of the post data: "&rememberme=on" to get a longer lasting cookie? That's what I think anyway... Seems like that at least!
So what could I be doing wrong If I'm sending the data right... Well because how else would it log in and give me a valid session cookie after sending the post data to do the login process? there's just something miniscule causing an issue.. Thanks!