Things to know (best practices and “issues”) READ IT !!! — uWSGI 2.0 documentationThings to know (best practices and “issues”) READ IT !!!¶ Obviously, never expose a socket speaking the uwsgi protocol to the public network unless you know what you are doing. That channel allows for dynamic loading of applications (read: arbitrary execution of code). The protocol is meant to be sanitized/validated by a proxy like nginx, apache, the uWSGI routers, etc. For example, if uwsgi uses
