ngrok's HTTP tunnels will work with CORS, but you cannot use ngrok's
--basic-auth option. ngrok's HTTP tunnels allow you to
specify basic authentication credentials to protect your tunnels. However,
ngrok enforces this policy on all requests, including the
requests that are required by the CORS spec. In this case, your
application must implement its own basic authentication.
There are certain configurations of ngrok which will result in certificate warnings. These usually happen when trying to use custom certificates with an ngrok domain. These can usually be solved by using a custom branded domain.
Yes, here is the official ngrok status page.
ngrok does not allow users to change the public ports on any reserved Domain or TCP Address. HTTPS and TLS tunnels will use port 443, and TCP tunnels will use the port assigned to you when the tunnel is created.
ngrok does not require nor provide static IP addresses. When you run the ngrok agent, it will update automatically as your public IP address changes, and you do not need to restart the agent. We do offer reserved Domains and TCP Addresses with our paid plans.
ngrok does not log or store any data transmitted through your tunneled connections. ngrok does log some information about the connections which are used for debugging purposes and metrics like the name of the tunnel and the duration of connections. For complete end-to-end security, use a TLS tunnel. Please see our Terms of Service and Data Processing Agreement for more information.
The first prototype for ngrok was committed on March 20th, 2013.