“Edit alogin, dont edit login. Edit both login and alogin, edit login, dont edit alogin. Place https…dont place https (in link).”
Which one of these actually work?
pushing RoS 6.47.9 and I wanna do is redirect user to certain page after trial users logs in.
Now, even if I do get a redirect, page closes once IP is given. Back in the day, redirect page use to stick until you close it.
Any cure, does anyone know the method that actually work?
I get an “Sign in…” on mobile phone. Once I click that, bam - browser closes. I want it to stick opened.
Will buy beer and chevaps if anyone places me in the right direction (Ive done thousand of builds in last couple of years..this one is really bugging me out).
thnx for any advice.
I stand to be corrected here, but you can’t have your cake and eat it.
OS’s ( Android, iOS, Linux, Windows, MAC - i.e. pretty much everything) does a check to a predefined list of URL’s once it connects to the WIFI. If it gets back a response from those URL’s but the response is not was it expected, it forces a type of browser to open (if it gets no response, it doesn’t even try open it).
This is to ensure users get access to website where they can easily login. Then (once the user has authenticated), if the OS detects it can now reach that page, it will close the browser (I think this is Android only - so far)
So you have 2 choices.
- Get back that HUGE headache from back in the day when you had to educate users to manually open their browser, hope and pray they don’t go to an https page that can’t be redirected, redirect them to your page and do your things the way you use to. This is not recommended as it users have become accustomed to the current way of life and will be left confused as to how to actually use your internet. You will also need to make sure to whitelist all domains that all OSes use to check if they are behind a hotspot
- Give up on the post auth redirect on certain operating systems