Re: [pfSense] Captive Portal REDIRURL$ / missing
On 02/27/13 14:10, Jim Pingle wrote: On 2/27/2013 6:23 AM, Frank Richter wrote: I'm using Version: *2.0.2-RELEASE * (amd64) and the captive portal is using https. That's already been fixed in 2.0.3 images, and discussed several times on the forum with workarounds/fixes. You can upgrade to a 2.0.3 snapshot (check the forum for links) or if you look in the commit history for the pfSense RELENG_2_0 branch on github you can find and apply the fix. Jim Thanks Jim for the hint. I added the / in /usr/local/captiveportal/index.php header(Location: https://{$ourhostname}/index.php?redirurl=; . urlencode(http://{$orig_host}*/*{$orig_request};)); header(Location: http://{$ourhostname}/index.php?redirurl=; . urlencode(http://{$orig_host}*/*{$orig_request};)); and it's working nicely now. ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
[pfSense] Captive Portal REDIRURL$ / missing
Hello, I'm using the captive portal for authentication purposes. a) A not yet authenticated user opens the browser and enters eg.:* http://de.wikipedia.org* He's redirected to the captive portal, authenticates and everything's fine. b) A not yet authenticated user opens the browser and enters eg.: *http://de.wikipedia.org/wiki/Pfsense* He's redirected to the captive portal, a closer look to the URL in the browser show: *...?redirurl...de.wikipedia.orgwiki* The / after the TLD is missing. The authentication succeeds but the result is of course: *Server not Found (...wikipedia.orgwiki) * I'm using Version: *2.0.2-RELEASE * (amd64) and the captive portal is using https. I'm pretty sure the missing / can be added somewhere, any ideas where? Thanks, Frank ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
Re: [pfSense] Captive Portal REDIRURL$ / missing
On 2/27/2013 6:23 AM, Frank Richter wrote: I'm using Version: *2.0.2-RELEASE * (amd64) and the captive portal is using https. That's already been fixed in 2.0.3 images, and discussed several times on the forum with workarounds/fixes. You can upgrade to a 2.0.3 snapshot (check the forum for links) or if you look in the commit history for the pfSense RELENG_2_0 branch on github you can find and apply the fix. Jim ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list