Recommended Posts


Recently I had to connect to a non-standard (non-443) port HTTPS webserver with Maxthon. It is not possible to change the inbound port on server. Upon entering: https://:, I got the following: "Error code 312 (net::ERR_UNSAFE_PORT)". A search yielded

Now here comes the question, if Maxthon is based on a Webkit, will this solution work for us?

Also, I would like to have these settings configurable in-browser (as I see these console-flags a clumsy anachronism). Please consider this improvement.

Link to comment
Share on other sites

Can this be "fixed"? Well, here's a quote from your superuser link:

You may be able to turn this off in Google Chrome, but you do so at your own risk. There is actually a good security reason why Chrome blocks these ports: Basically you open your browser up to being an open proxy for attackers to use to attack other services on your network.

For more information: Why does Chrome consider some ports unsafe?

I don't know what kind of server you have that you can't change the port, but did you try to use IE mode?

Link to comment
Share on other sites

I have read the article, no need to quote, thank you.

In case that Maxthon is unable to connect, I always have a Firefox as backup plan. But this is sad, I wish I could use Maxthon instead.

The server is some kind of secure remote control panel. Ports are fixed due to port-forwarding firewall policies, also 443 port is occupied by other service.

In Retro mode it is able to connect but some active elements are misaligned and/or non-functional.

I will test these 'chrome' flags shortly and post the results.

Link to comment
Share on other sites