Great Question - I asked it myself a long time ago… and turns out the answer is this.
From a purely security standpoint…
If the reverse proxy isn’t:
- Inspecting Traffic (MiM)
- Filtering URLs (ex. preventing access to /admin) ; or
- Requiring Authentication (at the proxy)
Then you might as well just port forward.
Because that’s essentially what you’re doing - forwarded unchecked traffic into your internal network (btw - not a great idea).
Note - there are 2 exceptions to this
- A reverse proxy could provide a more scalable approach to publishing web services as you can publish multiple services with the same IP address (and cert) all over the same port - where as a traditional port forwarding configuration would only allow you to use one IP per Port
- And the more modern use case is using a reverse proxy for translation from 443/to XYZ non-standard web port. This adds value because a web application running in linux over any port below 1024, requires the service run as root (your internet facing application SHOULD NEVER run with admin privileges).
Hope that helps,
(if anyone believes I’ve left anything out - or feels i’ve misstated something - please feel free to add/clarify)