I would suggest: write a sampler in Java that does the http put, then you can access the Response object and set the size to a value you specify. I think it would also work with the scripting samples (like Beanshell, Javascript)
I personally don't think there is anything to fix, as all samplers return the size of the response, and it would be confusing to have a model where the size is sometimes the request, sometimes the response, or a mix of the two. I'm a JMeter user, not a developer, so that's just my opinion, maybe I'm missing something obvious On Fri, Sep 30, 2016 at 8:54 PM, Ahmad A <anafo...@hotmail.com> wrote: > Hi IvanThank you for your prompt response. > The content-length that is being returned with the PUT request is actually > 0 > Content-Length: 0 > So I am guessing Jmeter is calculating the response size of all the > headers and text returned which is consistent with the 464 bytes recorded > for all object PUTs. This calculation of bytes for PUT is not correct since > the measurement needs to be the amount of data sent (PUT, POST) not > received (GET). > Is it possible to get this fixed?? > thanks > Ahmad > > > > From: ivan.ranc...@gmail.com > > Date: Fri, 30 Sep 2016 20:39:46 +0200 > > Subject: Re: HTTP PUT bytes output does NOT include the uploaded file > size > > To: user@jmeter.apache.org > > > > I would imagine JMeter returns the size of the http response, not the > size > > of the uploaded data. > > What does the Content-Length header return for your request? > > I would imagine it's a constant number, regardless of how many bytes you > PUT > > > > Example with wget, it's similar with curl > > wget -S -O /dev/null --method=PUT > > --body-data="123456789012345678901234567890 > 123456789012345678901234567890" > > http://... > > > > best regards > > Ivan > > >
