Are you returning response in good WSGI style, ie., returning
iterable, or are you using the write() callback returned by
start_response()?
Graham
> --
> You received this message because you are subscribed to the Google Groups "modwsgi" group.
> To post to this group, send email to mod...@googlegroups.com.
> To unsubscribe from this group, send email to modwsgi+u...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
>
>
Yep, you are seeing the messages because you are using the write()
callback and not catching the IOError and aborting the request
cleanly.
In mod_wsgi 3.X that should be the only place where it would be
evident to user code. The error can also occur when mod_wsgi consumes
a WSGI iterable, but in that case the error message will only appear
in the log files if LogLevel is debug.
Even for the latter case it used to be more noisy, but behaviour was
changed in 3.0. For details see:
http://code.google.com/p/modwsgi/issues/detail?id=29
Note that write() is not considered best practice and you should try
and return an iterable from WSGI application instead.
Graham