> On Sept. 4, 2014, 5:06 p.m., Dominic Hamon wrote: > > 3rdparty/libprocess/src/encoder.hpp, line 124 > > <https://reviews.apache.org/r/24984/diff/2/?file=676526#file676526line124> > > > > i'm not even sure how this was working given that Transfer-Encoding is > > an HTTP/1.1 feature.
I guess by virtue of all modern http clients which are very tolerable :) - Nikita ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/24984/#review52317 ----------------------------------------------------------- On Sept. 4, 2014, 9:28 a.m., Nikita Vetoshkin wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/24984/ > ----------------------------------------------------------- > > (Updated Sept. 4, 2014, 9:28 a.m.) > > > Review request for mesos. > > > Bugs: MESOS-1625 > https://issues.apache.org/jira/browse/MESOS-1625 > > > Repository: mesos-git > > > Description > ------- > > As mentioned in MESOS-1625 current HTTP Chunked Encoding implementation can > break clients (e.g. Tornado). As I see no need in Chunked-Encoding because we > know content size beforehand - I propose to use Content-Length. > > > Diffs > ----- > > 3rdparty/libprocess/src/encoder.hpp 9c5aa81 > > Diff: https://reviews.apache.org/r/24984/diff/ > > > Testing > ------- > > `make check` and manual testing with golang language native binding > > > Thanks, > > Nikita Vetoshkin > >
