4 ms·
the transport between reverse proxy <-> backend is not always http, eg python w/ uwsgi and php w/ fastcgi. And even when it is HTTP, as other commenters said,
by markasoftware 2y ago
the transport between reverse proxy <-> backend is not always http, eg python w/ uwsgi and php w/ fastcgi.
And even when it is HTTP, as other commenters said, the reverse proxy is able to handshake connections to the backend much more quickly than an actual remote client would, so it's still advantageous to use http/2 streams for the slower part of the connection.
- account42 2y ago> the transport between reverse proxy <-> backend is not always http, eg python w/ uwsgi and php w/ fastcgi. That's just called a web server and not a reverse proxy then. Both are just evolutions of CGI.