HTTPS authentication over WiFi using HttpClient 4

Question

I have Android pet-project DroidIn which utilizes HttpClient 4 (built into Android) to do some form based authentication. I started noticing that people who are using WiFi are reporting connection problems. It also doesn't help that site I'm accessing has self-assigned certificate. Well - the question is (I'm quite vague on WiFi details) If WiFi at the hotspot doesn't support HTTPS would that be a good enough reason for connection to fail and is there anything that I can do beside proxying into another appserver using HTTP which then would call HTTPS site?

Answer 1

wifi is just a low level protocol, you are dealing with HTTP & TCP/IP which is unaware of wifi. So you can ignore the fact that you are using wifi, just try to see if the server is accessible from the client side. (try a telnet on the https port which is 443 by default)

Answer 2

The wifi could be blocking the 443 port - but I'd be surprised since https is a pretty commonly used protocol by standard users. It if were blocked that could be your problem. slmix's answer would detect that case - but since you aren't with the client it probably isn't practical to run that telnet (even if android supported it).