top | item 44498119

(no title)

shelajev | 7 months ago

It took me an embarrassingly long time to internalize what the reverse proxy is. My brain got stuck on the fact that it is just proxying requests. What's so reverse about this? Silly.

discuss

order

happytoexplain|7 months ago

It's one of the classic cases of a thing being named relative to what came before it, rather than being named on its own merit. This makes sense to people working at the time the new thing is introduced, but is confusing to every other learner in the future.

raincom|7 months ago

What came before "reverse proxies"? Just curious to understand the history.

nosianu|7 months ago

Could be worse. All the many things named after people prevalent in some fields more than in others, biology/medicine for example. When you read, for example, "loop of Henle" or "circle of Willis" you don't even know where to begin. You either know the term or not.

azaras|7 months ago

Nowadays, "reverse" is suppressed in most ways. I have heard that Nginx is a proxy more often than a reverse proxy.

daveguy|7 months ago

How about service proxy vs web proxy rather than reverse proxy and proxy? Makes more clear that one is a proxy on the service side and the other is a proxy on the client side. Service proxy and Client proxy might be even better.

Valodim|7 months ago

Except in the configuration where you use the reversep_proxy directive, of course

rini17|7 months ago

Since web proxy was originally used near clients, caching stuff to save precious bandwidth of their kbps-tier connection.