Hey guys, I have some questions and was wondering if anyone had input on them.
1. Is it possible to send the output (STDOUT) from a cgi script to mod_wsgi? I guess that would be double-generating dynamic content per se. Im having issues where the ScriptAlias /cgi-bin/ /my_cgi-bin/ is processed first before the WSGIScriptAlias, so the url request for cgi-bin is never sent to mod_wsgi. I plan to have a web accelerator caching server infront of apache to always serve static content, so apache will only ever be seeing requests for html (unless the cache timeout runs out). 2. Whats the recommended way to send only html files to mod_wsgi, and serve the rest statically from apache? WSGIScriptAliasMatch /.*\.html$ /wsgi/wsgi_script.py - this seems to be the logical solution to me (only send html urls to mod_wsgi and apache the rest), but i noticed the environ['PATH_INFO'] is blank, and the REQUEST_URI doesn't remove hex and url formatting that PATH_INFO does. would WSGIScriptAlias / /wsgi/wsgi_script.py be better and then serve non-html files statically inside wsgi? 3. If i have a cache server infront of apache, and apache will barely never be serving up static content, would it make more sense to use embedded mode rather than daemon mode? Ive read daemon mode is good to delegate processes just to serve dynamic content and apache can continue to serve the static content, but 100% will be dynamically generated content, and if embedded mode is technically faster it sound like the right approach. Thanks guys, Joe S. -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
