> From this example and the previous one you posted it OK let's forget about my previous examples, lets focus on how to use internal router to print "hello" to console when a fastcgi request arrives.
> You can instruct the fastcgi parser to force a specific modifier with --fastcgi-modifier1 <n> (where n is the modifier1) It still doesn't work Let's compare uwsgi --workers 2 --http-socket :8080 --route ".* log:hello" --http-modifier1 5 uwsgi --workers 2 --fastcgi-socket :9000 --route ".* log:hello" --fastcgi-modifier 5 The only difference is http vs fastcgi. However, the first --http-socket displays "hello" to console, which is expected. The second --fastcgi-socket displays -- unavailable modifier requested: 5 -- On Tue, Jan 3, 2017 at 4:05 PM, Roberto De Ioris <[email protected]> wrote: > > > Hi guys, > > > > uwsgi --http-socket :8080 --route "/ log:hello" > > > > This one works by printing a "hello" to the stdout log. > > > > uwsgi --fastcgi-socket :9000 --route "/ log:hello" > > > > This one doesnt work > > > >> --- no python application found, check your startup logs for errors --- > > > > > From this example and the previous one you posted it looks like you are > not using the default modifier (the 0 one, mapped by default to python). > You can instruct the fastcgi parser to force a specific modifier with > --fastcgi-modifier1 <n> (where n is the modifier1) > > So if your main plugin is the 5 one: > > --fastcgi-modifier1 5 > > > -- > Roberto De Ioris > http://unbit.com > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi >
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
