3 ms·
These are often not enough ‘battle-tested” and come with a warning to never expose to public internet. So then you put a WAF in front of it, and you are back to
by winstonwinston 6mo ago
These are often not enough ‘battle-tested” and come with a warning to never expose to public internet. So then you put a WAF in front of it, and you are back to HTTP reverse proxy setup.
- nzeid 6mo agoI've always chuckled at this. Just don't used bad HTTP server libraries. I wouldn't put something like that on my intranet either. But even if you disagree with me the point is that I can count on only one hand the number of times I went "oh man, I need a FastCGI middle end".
- winstonwinston 6mo agoI agree with your point but this is the reality: F.E. Python stdlib http.server comes with a warning: Warning http.server is not recommended for production. It only implements basic security checks. The `standard` way is then to use WSGI or ASGI, not FastCGI, but it is similar interface implementation.