Jon, I'll take your "nope" as a correct answer, as I noted, I'm not current in HTTP/HTTPS, but as for it breaking the Internet or making firewalls redundant, what I was wondering is whether HTTP/HTTPS might have evolved an option (somewhat) like FTP's passive mode, i.e. first contact from client to server uses random client port and known/standard server port (80/443), but initial reply from server provides a new port number, on server, for client to use to continue the session.
If HTTP/HTTPS was doing something like this, the ACL, that looks good, would block the next outgoing HTTP/HTTPS packet.
More likely, though, it's something "simple", although as noted by others, more information would be very useful.
PS:
Oh, for anyone wondering would such a "dynamic" HTTP/HTTPS port change block such traffic on a firewall, maybe, maybe not. First, FW are often more "watchful" about what's trying to come in from the "outside", rather than internal traffic going out. Or, FWs, unlike basic ACLs, often inspect packets more deeply than ACLs, somewhat similar to what Cisco's NBAR might do.
Lastly, I have seen FWs break some new forms of traffic, until the FW software is updated. (Or, another example, "pure" PAT, without some form of embedded "fixups" breaks many protocols. Years ago, people often wondered why their Enterprise router would break some forms of Internet traffic, when you enabled PAT, but their home "router", also doing PAT, worked just fine.)
