> Thanks, Roberto!
>
> Does setting it to 0 disable it completely?
> Can I do the same via a reverse-rule?, e.g.
>
> route-if=startswith:${PATH_INFO};/ws harakiri:300with this rule you set harakiri to 300 seconds for requests starting with /ws. Take in account that the main harakiri (if lower) will be triggered first. > > > On Fri, Jun 20, 2014 at 10:22 PM, Roberto De Ioris <[email protected]> > wrote: > >> >> > Hi, there was a similar thread before >> > https://www.mail-archive.com/[email protected]/msg06413.html, >> > >> > but the question is a bit different, >> > >> > is it possible to disable harakiri for only a single request with the >> > uwsgi >> > python API? >> > >> > I have harakiri killing the app during "long" websocket requests >> often, >> > and >> > it's annoying that the app is reloaded when it actually shouldn't >> have. >> > >> > For all the rest of the requests I still want it, despite Roberto >> saying >> > that it does not work reliably in non-multiprocess modes. >> > >> > Thank you! >> > _______________________________________________ >> > uWSGI mailing list >> > [email protected] >> > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi >> > >> >> harakiri can be set via the routing framework too: >> >> route-if-not = startswith:${PATH_INFO};/ws harakiri:300 >> >> this will set harakiri to 300 for all the routes not starting with /ws >> >> -- >> Roberto De Ioris >> http://unbit.it >> _______________________________________________ >> 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 > -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
