User agents bug

Ask any support / help / issues / problem or question related to TumblingJazz
Post Reply
jrichards
Posts: 378
Joined: Tue Sep 22, 2015 11:58 pm

User agents bug

Post by jrichards »

When I generate cookies via Manual Browser Login and after some time I log-in via Browser Login, I have noticed, there are two active sessions in the tumblr account and both with different user agent (for example one session is FF43 on Win7 and second one is Chrome on OSX).

Is this by design, or is it a bug?

I'd expect, that the user agent is generated and binded to account when you first log in and then it stays same, until you reset it manually.

BTW having option to set user agent manually would be cool feature! :)
User avatar
martin@rootjazz
Site Admin
Posts: 34696
Joined: Fri Jan 25, 2013 10:06 pm
Location: The Funk
Contact:

Re: User agents bug

Post by martin@rootjazz »

should be sorted for next update, as will the ua viewer in the account details form
User avatar
martin@rootjazz
Site Admin
Posts: 34696
Joined: Fri Jan 25, 2013 10:06 pm
Location: The Funk
Contact:

Re: User agents bug

Post by martin@rootjazz »

Duck
Posts: 11
Joined: Fri Jan 20, 2017 8:26 pm

Re: User agents bug

Post by Duck »

There's another bug. When I open an account from TumblingJazz via "Browser login", it opens a chrome window, with ip from my settings for particular account. But user agent is wrong, it's always as my browser.
User avatar
martin@rootjazz
Site Admin
Posts: 34696
Joined: Fri Jan 25, 2013 10:06 pm
Location: The Funk
Contact:

Re: User agents bug

Post by martin@rootjazz »

I am not sure this should be a bug. It is awkward as setting a different UA string is detected by google for the captcha login and may be used to give you a more difficult / repeating captcha

Let me take a look, maybe can add an option
User avatar
martin@rootjazz
Site Admin
Posts: 34696
Joined: Fri Jan 25, 2013 10:06 pm
Location: The Funk
Contact:

Re: User agents bug

Post by martin@rootjazz »

https://rootjazz.com/tumblingjazz/updatetesting.html

It was a bug, I override whilst testing the signup routine and was meant to ignore it only for my machine but a logic bug ( a missing ! meant it applied to everyone
Post Reply