Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 27 subscribers
  • Views 8288 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

captive portal and hotspot certificate warning

christopher gilles

So any visit to a HTTPS site upon first browser attempt on a network with a captive portal or hotspot, will result in a certificate error on the browser.  

I've looked at other posts in the forum about the issue, but i'm still unclear as to how, or if you can actually make these warnings go away, and ensure that the first thing that pops up is the user login window, or the voucher window.

Whats another interesting occurrence, is sometimes if I enter HTTPS addresses,  such as in Safari,  I don't even get a warning,  just a "Safari cannot open the page"

I'd love to hear about other's experiences with this issue, and how they went about fixing or working around it.

Most likely since we have a lot of visitors, installing certificates on guest machines is not an option.

Thanks much :-)

C



This thread was automatically locked due to age.
Parents Reply Children
  • 0 in reply to Michael Dunn

    This make complete sense, of course when I think about it.  yes the warning is quite normal behavior and is to be expected on HTTPS pages.   It is indeed a browsers' normal behavior.  

    I'm wondering though what places such as starbucks does, with their free wifi.

    I note that when I go there, and attempt to go to a HTTPS site, at least in Chrome and Firefox, is it somehow manages to detect the captive portal, and instead of a warning message about the certificate, Chrome will open up a page that says something to the effect that the page doesn't load, you may have to connect to wifi by visiting their login link, as well as  also opening a new Tab with the captive portal page.

    I'd be interested in how people have managed any creative solutions, to make this a bit more functional.  There is of course the low tech solution of just telling your users they need to visit a HTTP site, but if there was a way to make it a bit more user friendly, I'd love to hear some peoples ideas.