Then I think the next step would be to take tcp dump on the apache side. On Fri, Feb 1, 2013 at 10:32 AM, Gandalf Corvotempesta <gandalf.corvotempesta@xxxxxxxxx> wrote: > I'm using apache with your fastcgi module. > > Il giorno 01/feb/2013 19:31, "Yehuda Sadeh" <yehuda@xxxxxxxxxxx> ha scritto: > >> The client can hang up the sending side of the socket, while still >> receiving data. It can also be an issue with some other middleman. >> Which web server are you using, which fastcgi module? >> >> On Fri, Feb 1, 2013 at 10:26 AM, Gandalf Corvotempesta >> <gandalf.corvotempesta@xxxxxxxxx> wrote: >> > I don't think this is a client issue because if client disconnect early >> > no >> > request is made and no error 400 will be sent. >> > >> > How will you send a response if no request is made? >> > >> > Il giorno 01/feb/2013 19:19, "Yehuda Sadeh" <yehuda@xxxxxxxxxxx> ha >> > scritto: >> > >> >> On Fri, Feb 1, 2013 at 9:51 AM, Gandalf Corvotempesta >> >> <gandalf.corvotempesta@xxxxxxxxx> wrote: >> >> > 2013/2/1 Yehuda Sadeh <yehuda@xxxxxxxxxxx>: >> >> >> Can you get just the sequence that fails (not the entire history)? >> >> > >> >> > Is the following enough? >> >> > http://pastebin.com/CS4MwdRf >> >> >> >> >> >> From what I can see, it looks like it's just receiving part of the >> >> expected data, might be the client disconnects early. >> >> >> >> Yehuda -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
