pfSense

Testing the Captive Portal in a Windows machine allowed me to see the URL it's hitting post login.

https://guest.example.com:8003/$portal_redirurl$

This obviously is incorrect and does not reflect the URL I configured (https://www.google.com) for the redirect.

I figured out the issue. It appears to be configuration problem, possible as a result of the upgrade. The default redirect URL I had configured was https://www.google.com. Somehow, it put that was the "After authentication Redirection URL" which was the variable $portal_redirurl$. After switching these 2 values in the configuration, it's now working.

Hi, Jim, I can confirm that something must have changed, possibly during the upgrade, between the two settings "Pre-authentication redirect URL" and "After authentication Redirection URL". I've always had "After authentication Redirection URL" set to "https://www.google.co.uk/" and this has always redirected the successfully connected user to this url after authentication.

However, this redirect recently stopped working. Moving the url to "Pre-authentication redirect URL" fixing the After authentication connection redirection. Which doesn't sound logical?

"After authentication Redirection URL" works for me when I have the client load the portal login page and login. After login, I get redirected to the URL set in the CP settings.

The change in #9819 made it so that if a client has its own redirect URL (for example, if they tried to load http://www.example.com and were redirected to the portal), that page gets loaded instead of the one set in the CP settings.

Perhaps we need a checkbox option to force the use of the post-auth redirect URL, but that wouldn't result in a 404 as described in the bug report here.