2009/1/28 gert <[email protected]>: > > Can you fix the server root for WSGIPythonPath > > meaning instead of doing > WSGIPythonPath /usr/httpd/www/appwsgi/www/lib > > ServerRoot "/usr/httpd" > WSGIPythonPath www/appwsgi/www/lib
No. It is very bad practice to be sticking standard Python modules under the Apache document root. This is for two reasons. The first is that a wrong configuration of Apache will mean that people can download your source code, including database logins and passwords if kept in those files. Second is that if using .py extensions for WSGI script files and Python path being set to be directory where WSGI script files are located, you can double import WSGI script files under file name. The latter occurs because mod_wsgi doesn't use standard Python module importer and so using 'import' for name of WSGI script file will import it a second time. Yes, I do realise that WSGI script files contain Python code, but in general they should only contain a very small wrapper for the entry point, with actual WSGI application code being imported from Python modules/packages elsewhere outside of the Apache document tree or any other directories exposed via Apache. > PS 2.2.11 and python 3 seems to work well :-) Are you now saying the POST problem has gone away. You haven't actually stated that the fix for memory issues did actually solve it. Or are you now actually supplying length to read(). Graham --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en -~----------~----~----~----~------~----~------~--~---
