Hi,
> The second response is a response to an expected follow up request on
> the same connection (using keep alive). If you're seeing it as part of
> the response on the first request then it's either an issue with the
> client not handling keep alive connections correctly, or an issue with
> the content length of the first response (need to verify that enough
> bytes were actually sent, can't do it with this trace dump).
What expected follow up request ?
The client never sent it in this case and for some case where there is
a follow up request (this happens too), how can the server decide that
there is an error _before_ receiving the request ???
In the example above it didn't have an impact, but sometimes, that
'500 error' is sent and then the client send another request and
interprets that '500' as the response to the request it just sent and
so gets a 500 error ...
Cheers,
Sylvain
_______________________________________________
ceph-users mailing list
ceph-users@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
