IMHO you're really confused. or got names wrong. or got things wrong. wsgi IS THE ONLY WAY to run python code for webservers. It's the only standardized spec to do so.
Nooow, if you're instead talinkg about mod_wsgi on apache, it's another matter entirely. Securing apache needs to be done by experts....if you're not, you can amuse yourself reading docs and chatting to peoples, but if you're really concerned the best option is to leave it to professionals. BTW, we "sponsor" nginx+uwsgi over apache for some time now. On Thursday, February 25, 2016 at 8:33:57 AM UTC+1, Robin Manoli wrote: > > Hello! > > I was recommended by #ubuntu-server on Freenode not to use wsgi. I wonder > if you recommend this as well (which means not using web2py with apache)? > > I'm wondering if there is certain type of web2py code I can look for to > prevent unauthorized access. In particular, how to prevent apache to send > GET requests to other domains than the actual web2py web site being > requested in the first place. > > I'd really appreciate your help on this :) > > - Robin > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
