What steps will reproduce the problem?
1. Launch with port 443
What is the expected output? What do you see instead?
Fails on permissions.
Please provide any additional information below.
Many corporate firewalls only allow outgoing HTTPS traffic on port 443.
For these situations, the listener MUST be there.
I'm currently just using a router to forward 443 to 4200, but that wouldn't
work for all people in all situations, so this is desirable. For me, since
I have control of iptables rules in my openwrt linux based router, it isn't
really a high priority. But I'm one of those whose workplace firewall will
not allow anything but HTTP on 80 and HTTPS on 443.
Original issue reported on code.google.com by TomOeh...@gmail.com on 18 Mar 2009 at 6:21
Original issue reported on code.google.com by
TomOeh...@gmail.com
on 18 Mar 2009 at 6:21