IP "0.0.0.0" and port "0" looks hardcoded to me: > plugins/corerouter/corerouter.c: memcpy(cs->client_address, "0.0.0.0", 7); > plugins/corerouter/corerouter.c: memcpy(cs->client_address, "0.0.0.0", 7); > plugins/corerouter/corerouter.c: memcpy(cs->client_address, "0.0.0.0", 7);
Or I'm reading memcpy wrong. 2013/3/5 Roberto De Ioris <[email protected]> > > > I've upgraded one FR to 1.9, it works fine so far, but I've noticed > > several > > errors: > > > > [uwsgi-fastrouter client_addr: 0.0.0.0 client_port: 0] > > fr_recv_uwsgi_header(): Bad address [plugins/fastrouter/fastrouter.c line > > 214] > > > > How to interpret these "Bad address"? Client sent request with bogus > > header? Which part of the header was invalid? > > > > > > Bad address refer to memory, so i suppose it is a bug somewhere, but as > your fastrouter is not crashing, i would bet that not managing unix > address correctly (you see 0.0.0.0) is causing some wrong error reporting > > > -- > Roberto De Ioris > http://unbit.it > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi > -- Łukasz Mierzwa
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
