captive-backend icon indicating copy to clipboard operation
captive-backend copied to clipboard

Figure out how to handle blocking https traffic if not authenticated

Open tomoconnor opened this issue 13 years ago • 2 comments
trafficstars

Currently, the captive portal isn't effective against https traffic (or actually, anything other than http). Figure out how to expand the current rule set to:

a) redirect a https request to the portal landing page.

b) block https traffic until authenticated.

tomoconnor avatar Nov 04 '12 21:11 tomoconnor

Shouldnt it probably just redirect all traffic to that box, on all ports?

cbetta avatar Nov 04 '12 22:11 cbetta

I thought about that.. Might require a subtly different ruleset.. Or some other TCP/UDP server running on the box to intercept and so on.

On Sun, Nov 4, 2012 at 10:04 PM, Cristiano Betta [email protected]:

Shouldnt it probably just redirect all traffic to that box, on all ports?

— Reply to this email directly or view it on GitHubhttps://github.com/tomoconnor/captive-backend/issues/4#issuecomment-10056112.

Tom O'Connor

http://tomoconnor.eu [email protected] twitter: @devopstom

tomoconnor avatar Nov 04 '12 22:11 tomoconnor