Hi Andreas,
Il 23/02/2016 13:46, Andreas Scheuring ha scritto:
Hi Riccardo,
those are my observations:
If I remove the --buffer-size parameter, the result from the curl is the
same (empty reply), but in the uwsgi log I see an error like this:
"invalid request block size: 8705 (max 4096)...skip"
This goes away as soon as I increase the buffer size!
Now using 127.0.0.1 instead of loopback:
$ curl -v 127.0.0.1:9090
* About to connect() to 127.0.0.1 port 9090 (#0)
* Trying 127.0.0.1...
* Connected to 127.0.0.1 (127.0.0.1) port 9090 (#0)
GET / HTTP/1.1
User-Agent: curl/7.29.0
Host: 127.0.0.1:9090
Accept: */*
* Empty reply from server
* Connection #0 to host 127.0.0.1 left intact
curl: (52) Empty reply from server
[snip]
Are there any other knobs that I could use to get more debug traces? I'm
kind of lost in debugging this as the uwsgi does not show any outputs on
my requests... (it does only, if the buffer size is too small)
CFLAGS=-DUWSGI_DEBUG pip install should result in a more verbose uwsgi build
So you're saying the only way to execute test cases is with a travis CI?
Yeah, we don't have unit test for C code we have to track down it. Or take this
as a good occasion to start writing C tests.
--
Riccardo Magliocchetti
@rmistaken
http://menodizero.it
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
