On Tue, Sep 2, 2014 at 3:08 PM, Javier Guerra Giraldez <jav...@guerrag.com> wrote:
> FastCGI isn't a Django concern, as it is a WSGI-only framework (like > most Python frameworks). flup used to be a reasonable FastCGI WSGI > container, but it's no longer supported, so it's unreasonable to ask > the Django foundation to support it. > > the question is: what options are there to run WSGI under IIS? my > first guess would be any HTTP-WSGI container (gunicorn?) and set IIS > as a proxy. The answer is: copy/paste the flup bridge code from an old version of Django. Nothing in Django attempts to detect use of FastCGI and crash when discovered. Rather, Django just no longer ships a FastCGI-to-WSGI bridge, so deployments which use FastCGI will need to provide their own. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAL13Cg_Z2FEtkxzrSwi8u2880q8oGeKpxg2%3DAnmbtGG3O%2Bj-rw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
