> 2010/9/23 Jean-Baptiste Quenot <[email protected]>:
> Sep 23 21:41:28 bl1 nginx: 77.87.104.81 - 0 29.995 29.995 "GET
> /exit?u=http%3A//www.hotelchaumierechamonix.com HTTP/1.1" 302 0
> "http://fr.nomao.com/1350937.html"; "Mozilla/5.0 (Windows; U; Windows
> NT 5.1; fr; rv:1.9.2.10) Gecko/20100914 Firefox/3.6.10 ( .NET CLR
> 3.5.30729)" "82.242.155.208" "fr.nomao.com"
>
> So uwsgi answered in 434 msecs at 21:40:58, but apparently nginx was
> still waiting for the answer and got a client abort 30 seconds later
> at 21:41:28.
Nginx waits if the uWSGI socket is not closed, but even if there is a bug
in uWSGI why it does not timeout and simply close connection after 29.xxx
seconds...
That is very strange, i will try to reproduce the error leaving the socket
opened to see if nginx returns in teh same way.
> Sep 23 21:47:30 bl5 nginx: 77.87.104.81 - 0 30.004 30.004 "GET
> /ajax/search?q=8%20route%20de%20genlis%20arc%20sur%20tille%2021130&b=(5.264854431152344,47.379521907289295),(5.12237548828125,47.30507670600022)&time=1285271224385
> HTTP/1.1" 200 0
>
Nginx is losing 40k of data that uWSGI has sent ??? that is embarassing
> And yet another one because I'm really looking forward to convince you :-)
>
> [pid: 18127|app: 0|req: 505/10887] 77.87.104.81 () {48 vars in 1266
> bytes} [Thu Sep 23 21:48:50 2010] GET /hit.png?type=map-load&time=110
> => generated 0 bytes in 433 msecs (HTTP/1.1 200) 1 headers in 59 bytes
> (0 async switches on async core 0)
>
>
0 bytes from uWSGI is normal ?
--
Roberto De Ioris
http://unbit.it
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
