Tag Info

Hot answers tagged


It is very likely those will be blocked, especially in corporate networks or on public wifi. Less likely on a regular home internet connection. It would certainly be blocked on my work network. In addition, people will have to remember to type the port number to get to your site, which is an extra headache you don't want to deal with. For internal or ...


To use protocol specific features you have to use the appropriate mode. Mode tcp gives you only access to tcp specific features, but to get http specific features like choosing the backend based on the URI you need to have mode http. Unfortunately HTTP/2 looks very different from HTTP/1.x and is not support by mode http currently so you have to use mode ...


Corporate networks will usually be defaulted to rules like this: deny all; allow 80; allow 443; allow 21; allow 22; etc... It is much easier to configure this way rather than to explicitly deny 99% of the 65,535 available ports. With that said, I took over a client-facing portal which used a non-standard port due to network limitations; I do not know the ...


Its not hard to make your browser hit say http://example.com:8080/index.html, but when you talk about corporate policies blocking non standard ports that seems mighty difficult. If you have some sort of Load balancing set up, you can still set up your applications to run on a standard port and have the load balancer port forward to the odd port internally. ...


I had this problem but with a site that stopped working after a Firefox upgrade. The Fix: Change Firefox security settings. It seems Firefox is disabling older ssl standards. In Firefox address bar enter about:config In search enter security.ssl3 Toggle false values to true You should now be able to get to your sites.


It turned out there was already a vhost in ssl.conf that was overiding my settings. School boy error.


Try this: https://flokkstudios.com:8443 When using a non standard https port, like 8443, you need to add https in the URL. Otherwise the browser supposes it's http traffic, non encrypted, and thus displays encrypted content directly, which results in these strange characters.

Only top voted, non community-wiki answers of a minimum length are eligible