Right, the we should call strict_strtoll() instead. I opened issue #10701, and sent a pull request for the fix. Thanks, Yehuda On Fri, Jan 30, 2015 at 10:01 AM, Axel Dunkel <ad@xxxxxxxxx> wrote: > > > >> > Telling from the source code the issue seems not to be that the > content >> > lengths do not match, rather that the http-header Content-Length is > not >> > parseable (allthough the header is displayed fine in the debug > output). If >> > strict_strtol returns an error, to be exact - ? >> > >> >> In that case the time is meaningless. How big is Content-Length when > it fails? > > CONTENT_LENGTH=2147483648 > just a bit too much for a long - ? > > Best regards > Axel Dunkel > > -- > 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 -- 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