4 ms·

Not everything on top of HTTP comes through the browser, either ;)

• bombcar 5y ago
  More and more APIs use HTTP as the transport for various reasons, but one of them is that HTTP has considered large number of edge cases and has been tested "in the fire" - rolling your own custom API with security and encryption is much more fraught with dangers.
  • pjmlp 5y ago
    Except HTTP 2.0/3.0 has very little to do with HTTP 1.0, and is more akin to use TCP/UDP directly anyway. It just happens to get a free pass over port 80.
    • bombcar 5y ago
      And that's the other major reason - if your traffic LOOKS like web traffic, it will slip through firewalls and other middle-ware devices.
  • secondcoming 5y ago
    But I would bet that those only use the GET or POST functionality of HTTP, and that the real reason it's used is because it's easy to quickly get something up an running. It's a short-term gain, but quite inefficient in the long run. ZeroMQ is a perfectly valid replacement for HTTP in internal networks. There's no reason for everything to be human readable.