>>
> >> > Hi I would argue that many users will benefit from adding a metric to
> >> > calculate the sent bytes for PUT and POST.
> >> > I was wondering can someone create a bug for this (or point me to how
> to
> >> > create one? I have not
users will benefit from adding a metric to
>> > calculate the sent bytes for PUT and POST.
>> > I was wondering can someone create a bug for this (or point me to how to
>> > create one? I have not created a jmeter bug before).
>> > Is there anytime line for this fun
; > calculate the sent bytes for PUT and POST.
> > I was wondering can someone create a bug for this (or point me to how to
> > create one? I have not created a jmeter bug before).
> > Is there anytime line for this functionality?
> > thanks
> > Ahmad
> >
.
>> I was wondering can someone create a bug for this (or point me to how to
>> create one? I have not created a jmeter bug before).
>> Is there anytime line for this functionality?
>> thanks
>> Ahmad
>>
>> > Subject: Re: HTTP PUT bytes output does NOT
create a bug for this (or point me to how to
> create one? I have not created a jmeter bug before).
> Is there anytime line for this functionality?
> thanks
> Ahmad
>
> > Subject: Re: HTTP PUT bytes output does NOT include the uploaded file
> size
> > To: user@jmeter.apa
Hello,
the guidelines for entering enhancements requests in Bugzilla are here
http://jmeter.apache.org/issues.html
there are also links to existing enhancement requests and bugs, it might be
good to check if there's already a similar request
hope it helps
On Mon, Oct 3, 2016 at 5:18 PM, Ahmad A
Ahmad
> Subject: Re: HTTP PUT bytes output does NOT include the uploaded file size
> To: user@jmeter.apache.org
> From: ser...@bosoconsulting.it
> Date: Sat, 1 Oct 2016 21:36:34 +0200
>
> HI ,
>
> thumbs up for a new metric measuring output bytes.
> It should not break
HI ,
thumbs up for a new metric measuring output bytes.
It should not break any current report, but I have this need very often.
It is a common requirement for many application types like document management.
Also, it is not so simple to forecast the output size, when considering
cookies, heade
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).
> >> I
??
>> 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
>> >
&
gt; 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
&g
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
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
13 matches
Mail list logo
