What is the default TCP port for HTTP and HTTPS respectively, and why can these defaults matter in security configurations?

• A.HTTP: 8080, HTTPS: 8443 - these often matter because reverse proxies and container platforms default to these ports internally, and firewalls often block the well-known ports 80 and 443 outright by default, forcing operators to open the alternate ports for any internal service that expects to be reachable
• B.HTTP: 80, HTTPS: 443 - knowing the defaults matters because firewall rules, WAFs, and browser security policies often apply differently to well-known ports versus custom ports; for example, HSTS applies to port 443 and browsers apply stricter mixed-content rules to port 80
• C.HTTP: 21, HTTPS: 22 - these often matter because file transfer and remote administration traffic is commonly routed through the same ports as ordinary web traffic on shared hosting providers that rarely separate protocols by port range
• D.HTTP: 443, HTTPS: 80 - these often matter because browsers historically reversed the assignment before the registry was finalized, and some legacy servers still expect the swap during initial protocol negotiation