{"id":294,"date":"2021-01-03T08:01:02","date_gmt":"2021-01-03T02:31:02","guid":{"rendered":"http:\/\/madhurendra.com\/?p=294"},"modified":"2021-01-07T04:41:42","modified_gmt":"2021-01-06T23:11:42","slug":"blocking-port-80-wont-help-you","status":"publish","type":"post","link":"https:\/\/madhurendra.com\/blocking-port-80-wont-help-you\/","title":{"rendered":"Why just blocking port 80 won’t help you"},"content":{"rendered":"\n
We know HTTP is insecure since across the web IANA’s assigned port list<\/a> is used by default which says port 80 should be used for HTTP traffic, but it’s not that you cannot run anything else which is “non-standard” in port 80. <\/p>\n\n\n\n Anyways, coming to point you could be running HTTP server on any port 80, 8080, 8090 whatever, HTTP protocol by design is left insecure. Since we cannot change the standard 80 usage everywhere (IPv6 is still on way even after decades) there are multiple remediations that can be used to avoid common challenges with HTTP. <\/p>\n\n\n\n <\/p>\n","protected":false},"excerpt":{"rendered":" We know HTTP is insecure since across the web IANA’s assigned port list is used by default which says port 80 should be used for HTTP traffic, but it’s not that you cannot run anything else which is “non-standard” in port 80. Anyways, coming to point you could be running HTTP server on any port … <\/p>\n