[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 13/06/13 09:23, Gordon Henderson wrote: > > But you're right - there are no standard for captive portals, but > in all the ones I've used, I've only seen 2 ways it's accomplished > - one uses DNS to direct all web requests to an internal page and > the other force re-directs web traffic. > > The force redirect is more efective in my experience - and I've > designed systems that use both. It's likely to depend if the port 80 redirect operates at the IP level or if it operates at the HTTP level. The former (along with the DNS method) will most likely enable a browser with a proxy exception to communicate with your portal. Since so far as the browser is concerned it is using a URL it is able to access directly. Using an HTTP redirect is likely to fail since it's unlikely that the resulting URL will match any proxy exceptions in the browser. Note that the IE "Bypass Proxy Server for Local Addresses" option dosn't do anything like comparing the IP address of the target URL against the IP address(es) and netmask(s) of the machine. Which would probably be very useful in this context. Of course you are still going to be entirely stuffed with a device which dosn't have a web browser. E.g. a Wi-Fi SIP phone or one where the "web browser" actually runs in a data centre somewhere else. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlG6JJYACgkQsoRLMhsZpFevPgCfUHZgMDiMDYHxJXf6GGMiMUO2 SRYAnj94aRD6/oJB8yLd2nDIG8d7rEYb =HRfw -----END PGP SIGNATURE----- -- The Mailing List for the Devon & Cornwall LUG http://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/listfaq