2009/1/28 gert <[email protected]>:
>
> On Jan 28, 2:41 am, Graham Dumpleton <[email protected]>
> wrote:
>> 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.
>
> That's why it say's SERVER-root :) not DOCUMENT-root

My mistake in reading.

Still the same answer. I do not see any value in doing this as it
wouldn't even be the norm that people would want to stick stuff under
the server 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.
>
> ok i need sleep right now and need to read this a few times before i
> can say something non stupid here.

When you do read it, remember I was thinking you were talking about
document root. :-)

>> > 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().
>
> yep and i have no idea why it works now, i can only say this
> 2.2.11 source py3 source r1167 trunk works great except for the
> serverRoot bug :P

I can guess, but wouldn't know for sure unless you reverted to code
from before fix and ran it with the C code level debug as I asked you
to do in the first place before updating to latest. Wish you would
just do what I ask, you always jump ahead and I can never collect the
proper information I need to validate what the issue may have been in
the first place, even if my educated guesses may be correct. :-(

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
-~----------~----~----~----~------~----~------~--~---

Reply via email to