Another Apache *.conf is invoked prior to the one included above containing
WSGIDaemonProcess app user=apache processes=3 threads=1 Bottom line: how can I get Apache to call the script named in ErrorDocument while any Django HttpResponse return from my server-side-django-script does *NOT* activate and call the ErrorDocument script? I.e. my django-server-side-script implementing my API can return JSON text with specified HTTP error codes directly to the client without triggering the ErrorDocument script, *AND* any HTTP error encountered in Apache *BEFORE* getting to my django-server-side-script will invoke the ErrorDocument script. I could also tolerate a configuration where Apache trapped error codes, e.g. Unauthorized, somehow call a function within my django-server-side-script. The issue is that as-is now, Apache caught errors work fine, but any Django HttpResponse return from my server-side-django-script is also triggering and running the ErrorDocument script which looses the text and HTTP error code that was sent as per the Django HttpResponse return from my server-side-django-script and intended to get to the client. -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/modwsgi. For more options, visit https://groups.google.com/d/optout.
