Reverse proxies usually require configuration changes to work. Plus they are single points of failure. Server Name Indication (SNI) is a fairly recent development as well - any apps written before that was widespread, or designed in that way, will have a unique web server for every HTTP based service that has its own separately managed certificate.
Reverse proxying is less common in wild IoT devices, network appliances, and certain kinds of enterprise/line-of-business apps... Surprisingly Microsoft IIS seems to be an exception in that area
oakwhiz|3 years ago
Reverse proxying is less common in wild IoT devices, network appliances, and certain kinds of enterprise/line-of-business apps... Surprisingly Microsoft IIS seems to be an exception in that area
horsawlarway|3 years ago
Plus - Unless the client is outside of a browser context, you can drop an nginx instance in front of the service without the service having any clue.
Throw a load balancer in front and it's probably much more robust than a single service.
Honestly - reverse proxy support is one of the more magical parts of http.