That will not help at all. That can’t unblock the request which is already running inside of Apache. It would still keep running regardless.
You can only get the sort of functionality you want by using Linux. Windows is not a very good platform for Python web application deployment as you are restricted by how Apache works on that platform. Graham > On 13 Dec 2016, at 7:49 PM, [email protected] wrote: > > Would it be helpful if i'll wrap it with Nginx and set the timeout from there? > > On Tuesday, December 13, 2016 at 1:12:27 AM UTC+2, Graham Dumpleton wrote: > >> On 13 Dec 2016, at 1:03 AM, [email protected] <> wrote: >> >> I've set in httpd.conf >> >> Timeout 2 >> >> and in access.log response time is bigger the 20 seconds sometimes. >> >> any ideas why the Timeout doesn't work? > > Because Timeout in Apache is not an application request timeout. > > The documentation for Apache says: > > Description: > <http://httpd.apache.org/docs/2.4/mod/directive-dict.html#Description> > Amount of time the server will wait for certain events before failing a > request > Syntax: <http://httpd.apache.org/docs/2.4/mod/directive-dict.html#Syntax> > TimeOut seconds > Default: <http://httpd.apache.org/docs/2.4/mod/directive-dict.html#Default> > TimeOut 60 > Context: <http://httpd.apache.org/docs/2.4/mod/directive-dict.html#Context> > server config, virtual host > Status: <http://httpd.apache.org/docs/2.4/mod/directive-dict.html#Status> > Core > Module: <http://httpd.apache.org/docs/2.4/mod/directive-dict.html#Module> > core > The TimeOut directive defines the length of time Apache httpd will wait for > I/O in various circumstances: > > When reading data from the client, the length of time to wait for a TCP > packet to arrive if the read buffer is empty. > > For initial data on a new connection, this directive doesn't take effect > until after any configured AcceptFilter > <http://httpd.apache.org/docs/2.4/mod/core.html#acceptfilter> has passed the > new connection to the server. > > When writing data to the client, the length of time to wait for an > acknowledgement of a packet if the send buffer is full. > In mod_cgi <http://httpd.apache.org/docs/2.4/mod/mod_cgi.html>, the length of > time to wait for output from a CGI script. > In mod_ext_filter <http://httpd.apache.org/docs/2.4/mod/mod_ext_filter.html>, > the length of time to wait for output from a filtering process. > In mod_proxy <http://httpd.apache.org/docs/2.4/mod/mod_proxy.html>, the > default timeout value if ProxyTimeout > <http://httpd.apache.org/docs/2.4/mod/mod_proxy.html#proxytimeout> is not > configured. > > So the timeout relates to blocking events which can affect Apache when it is > communication over a docket connection. > > Although for mod_cgi it also acts a form of request timeout, it doesn’t in > mod_wsgi. > > The only equivalent in mod_wsgi is available in daemon mode and is the > request-timeout option to WSGIDaemonProcess. Because you are on Windows > though, you can’t use daemon mode as that requires a UNIX type operating > system. > > In short, for Apache request handlers that run inside of the Apache worker > processes themselves, there is no concept of a request timeout. This applies > not just to mod_wsgi in embedded mode but any other Apache module which runs > applications embedded in Apache. > > Graham > > > > > -- > 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] > <mailto:[email protected]>. > To post to this group, send email to [email protected] > <mailto:[email protected]>. > Visit this group at https://groups.google.com/group/modwsgi > <https://groups.google.com/group/modwsgi>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- 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 https://groups.google.com/group/modwsgi. For more options, visit https://groups.google.com/d/optout.
