Timeline for What is a "reverse proxy" in webmastering?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 8, 2021 at 8:51 | comment | added | Zach Lipton | @Fabich It's common in some stacks to want to separate the web server, which can be hardened to deal with random internet traffic and optimized to serve small static files very quickly, from the application server, which has heavy threads/processes with considerable overhead (interpreter with all necessary libraries loaded and initialized, database connection, etc...). Any model like this means the web server needs a protocol to pass the request data to the application server. That protocol might be HTTP or it might be something like like uwsgi. | |
| Feb 8, 2021 at 8:34 | comment | added | Davor | @Fabich - people do exactly that with Node.js. So I guess the answer is they work with a language that is not supported by Nginx. | |
| Feb 8, 2021 at 8:23 | comment | added | Fabich | Why would you intentionally use a server with some missing features if you actually need the features and need to add Nginx after that ? Why not directly serve it with Nginx ? | |
| Feb 8, 2021 at 8:12 | review | First posts | |||
| Feb 8, 2021 at 10:01 | |||||
| Feb 8, 2021 at 8:04 | history | answered | Zach Lipton | CC BY-SA 4.0 |