[pfSense] Captive portal and HTTPS homepage
Hi, We've got pfSense 2.1 snapshots running with Squid package 2.7.9 pkg v.4.3.1 (not sure if it's meaningful or not) If a client behind the captive portal is not authenticated yet, and its browser's homepage is an https:// URL (typically our University's webmail), then there's no redirection to the captive portal to force the user to authenticate, and the page keeps loading forever with an empty browser window. If we change the client's browser's homepage to an http:// page, then all is fine. How can we fix this problem ? Thanks in advance -- Jérôme Alet - jerome.a...@univ-nc.nc - Direction du Système d'Information Université de la Nouvelle-Calédonie - BPR4 - 98851 NOUMEA CEDEX Tél : +687 290081 Fax : +687 254829 ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
Re: [pfSense] Captive portal and HTTPS homepage
On Sun, Nov 25, 2012 at 10:50 PM, Jerome Alet jerome.a...@univ-nc.nc wrote: Hi, We've got pfSense 2.1 snapshots running with Squid package 2.7.9 pkg v.4.3.1 (not sure if it's meaningful or not) If a client behind the captive portal is not authenticated yet, and its browser's homepage is an https:// URL (typically our University's webmail), then there's no redirection to the captive portal to force the user to authenticate, and the page keeps loading forever with an empty browser window. If we change the client's browser's homepage to an http:// page, then all is fine. How can we fix this problem ? We don't intercept HTTPS traffic because it would require causing an ugly cert error. There is no work around (short of getting in and changing the source yourself) at this time. ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
