You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jmeter.apache.org by Philippe Mouawad <ph...@gmail.com> on 2013/04/11 23:23:21 UTC
Re: JMeter returns 204 code when URL is found in cache
Hello Sebb, Milamber, Rainer,
What's your thoughts on that ?
Regards
Philippe
On Sun, Mar 31, 2013 at 9:40 PM, Philippe Mouawad <
philippe.mouawad@gmail.com> wrote:
> Created:
> https://issues.apache.org/bugzilla/show_bug.cgi?id=54778
>
>
> On Fri, Mar 29, 2013 at 10:27 PM, Shmuel Krakower <sh...@gmail.com>wrote:
>
>> OK, yeah it is true, but as I don't have sources of JMeter in hand, I
>> would
>> guess that the referenced piece of code is calling to either:
>>
>> http://jmeter.apache.org/api/org/apache/jmeter/protocol/http/sampler/HTTPSampleResult.html#setResponseNoContent()
>> which it shouldn't? or to:
>>
>> http://jmeter.apache.org/api/org/apache/jmeter/samplers/SampleResult.html#setResponseCode(java.lang.String)
>>
>> which can accept any string, without any restrictions/rules. Thus if it
>> was
>> up to me, I would set it to "Cached" instead of "204".
>>
>> Shmuel Krakower.
>> www.Beatsoo.org - re-use your jmeter scripts for application performance
>> monitoring from worldwide locations for free.
>>
>>
>> On Sat, Mar 30, 2013 at 12:07 AM, Philippe Mouawad <
>> philippe.mouawad@gmail.com> wrote:
>>
>> > I didn't notice it myself, I found it in a tweet:
>> >
>> > - https://twitter.com/Scooletz/status/317252989003915264
>> >
>> > I didn't check code at first and was surprised by answer.
>> > Then looking at Http Impl I first thougth it was a bug in HC4 but it's
>> like
>> > this everywhere.
>> >
>> >
>> > On Fri, Mar 29, 2013 at 10:01 PM, Shmuel Krakower <shmulikk@gmail.com
>> > >wrote:
>> >
>> > > Hi,
>> > > Good point, although I haven't noticed it myself.
>> > >
>> > > Usually on browser developers tools you will see instead of an HTTP
>> > > response code, a "cache" note or something mentioning the request
>> served
>> > by
>> > > local cache. I guess this should be the case where requests are
>> served by
>> > > the Cache in JMeter.
>> > > The only question is if the response code of HTTP Sampler must be a
>> valid
>> > > HTTP numeric response code, or can simply contain "cached" string.
>> > >
>> > > Best,
>> > >
>> > > Shmuel Krakower.
>> > > www.Beatsoo.org - re-use your jmeter scripts for application
>> performance
>> > > monitoring from worldwide locations for free.
>> > >
>> > >
>> > > On Fri, Mar 29, 2013 at 11:52 PM, Philippe Mouawad <
>> > > philippe.mouawad@gmail.com> wrote:
>> > >
>> > > > Hello,
>> > > > I noticed looking at Http implementations this day that when using
>> > Cache
>> > > > Manager and if URL was cached
>> > > > jmeter returned code 204.
>> > > >
>> > > > Looking at this code definition, it does not seem to be a good
>> response
>> > > no
>> > > > ?
>> > > >
>> > > >
>> > > >
>> > >
>> >
>> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>> > > >
>> > > > * The server has fulfilled the request but does not need to return
>> an
>> > > > entity-body, and might want to return updated metainformation. The
>> > > response
>> > > > MAY include new or updated metainformation in the form of
>> > entity-headers,
>> > > > which if present SHOULD be associated with the requested variant. *
>> > > > * *
>> > > >
>> > > > * If the client is a user agent, it SHOULD NOT change its document
>> view
>> > > > from that which caused the request to be sent. This response is
>> > primarily
>> > > > intended to allow input for actions to take place without causing a
>> > > change
>> > > > to the user agent's active document view, although any new or
>> updated
>> > > > metainformation SHOULD be applied to the document currently in the
>> user
>> > > > agent's active view. *
>> > > > * *
>> > > >
>> > > > * The 204 response MUST NOT include a message-body, and thus is
>> always
>> > > > terminated by the first empty line after the header fields. *
>> > > >
>> > > >
>> > >
>> >
>> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>> > > > *
>> > > > *
>> > > > In fact as in this case no request is made to server, it is hard to
>> say
>> > > > what should be the response.*
>> > > > *
>> > > > --
>> > > > Cordialement.
>> > > > Philippe Mouawad.
>> > > >
>> > >
>> >
>> >
>> >
>> > --
>> > Cordialement.
>> > Philippe Mouawad.
>> >
>>
>
>
>
> --
> Cordialement.
> Philippe Mouawad.
>
>
>
--
Cordialement.
Philippe Mouawad.
Re: JMeter returns 204 code when URL is found in cache
Posted by Philippe Mouawad <ph...@gmail.com>.
A bump on this one
On Thu, Apr 11, 2013 at 11:23 PM, Philippe Mouawad <
philippe.mouawad@gmail.com> wrote:
> Hello Sebb, Milamber, Rainer,
> What's your thoughts on that ?
> Regards
> Philippe
>
>
> On Sun, Mar 31, 2013 at 9:40 PM, Philippe Mouawad <
> philippe.mouawad@gmail.com> wrote:
>
>> Created:
>> https://issues.apache.org/bugzilla/show_bug.cgi?id=54778
>>
>>
>> On Fri, Mar 29, 2013 at 10:27 PM, Shmuel Krakower <sh...@gmail.com>wrote:
>>
>>> OK, yeah it is true, but as I don't have sources of JMeter in hand, I
>>> would
>>> guess that the referenced piece of code is calling to either:
>>>
>>> http://jmeter.apache.org/api/org/apache/jmeter/protocol/http/sampler/HTTPSampleResult.html#setResponseNoContent()
>>> which it shouldn't? or to:
>>>
>>> http://jmeter.apache.org/api/org/apache/jmeter/samplers/SampleResult.html#setResponseCode(java.lang.String)
>>>
>>> which can accept any string, without any restrictions/rules. Thus if it
>>> was
>>> up to me, I would set it to "Cached" instead of "204".
>>>
>>> Shmuel Krakower.
>>> www.Beatsoo.org - re-use your jmeter scripts for application performance
>>> monitoring from worldwide locations for free.
>>>
>>>
>>> On Sat, Mar 30, 2013 at 12:07 AM, Philippe Mouawad <
>>> philippe.mouawad@gmail.com> wrote:
>>>
>>> > I didn't notice it myself, I found it in a tweet:
>>> >
>>> > - https://twitter.com/Scooletz/status/317252989003915264
>>> >
>>> > I didn't check code at first and was surprised by answer.
>>> > Then looking at Http Impl I first thougth it was a bug in HC4 but it's
>>> like
>>> > this everywhere.
>>> >
>>> >
>>> > On Fri, Mar 29, 2013 at 10:01 PM, Shmuel Krakower <shmulikk@gmail.com
>>> > >wrote:
>>> >
>>> > > Hi,
>>> > > Good point, although I haven't noticed it myself.
>>> > >
>>> > > Usually on browser developers tools you will see instead of an HTTP
>>> > > response code, a "cache" note or something mentioning the request
>>> served
>>> > by
>>> > > local cache. I guess this should be the case where requests are
>>> served by
>>> > > the Cache in JMeter.
>>> > > The only question is if the response code of HTTP Sampler must be a
>>> valid
>>> > > HTTP numeric response code, or can simply contain "cached" string.
>>> > >
>>> > > Best,
>>> > >
>>> > > Shmuel Krakower.
>>> > > www.Beatsoo.org - re-use your jmeter scripts for application
>>> performance
>>> > > monitoring from worldwide locations for free.
>>> > >
>>> > >
>>> > > On Fri, Mar 29, 2013 at 11:52 PM, Philippe Mouawad <
>>> > > philippe.mouawad@gmail.com> wrote:
>>> > >
>>> > > > Hello,
>>> > > > I noticed looking at Http implementations this day that when using
>>> > Cache
>>> > > > Manager and if URL was cached
>>> > > > jmeter returned code 204.
>>> > > >
>>> > > > Looking at this code definition, it does not seem to be a good
>>> response
>>> > > no
>>> > > > ?
>>> > > >
>>> > > >
>>> > > >
>>> > >
>>> >
>>> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>>> > > >
>>> > > > * The server has fulfilled the request but does not need to return
>>> an
>>> > > > entity-body, and might want to return updated metainformation. The
>>> > > response
>>> > > > MAY include new or updated metainformation in the form of
>>> > entity-headers,
>>> > > > which if present SHOULD be associated with the requested variant. *
>>> > > > * *
>>> > > >
>>> > > > * If the client is a user agent, it SHOULD NOT change its document
>>> view
>>> > > > from that which caused the request to be sent. This response is
>>> > primarily
>>> > > > intended to allow input for actions to take place without causing a
>>> > > change
>>> > > > to the user agent's active document view, although any new or
>>> updated
>>> > > > metainformation SHOULD be applied to the document currently in the
>>> user
>>> > > > agent's active view. *
>>> > > > * *
>>> > > >
>>> > > > * The 204 response MUST NOT include a message-body, and thus is
>>> always
>>> > > > terminated by the first empty line after the header fields. *
>>> > > >
>>> > > >
>>> > >
>>> >
>>> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>>> > > > *
>>> > > > *
>>> > > > In fact as in this case no request is made to server, it is hard
>>> to say
>>> > > > what should be the response.*
>>> > > > *
>>> > > > --
>>> > > > Cordialement.
>>> > > > Philippe Mouawad.
>>> > > >
>>> > >
>>> >
>>> >
>>> >
>>> > --
>>> > Cordialement.
>>> > Philippe Mouawad.
>>> >
>>>
>>
>>
>>
>> --
>> Cordialement.
>> Philippe Mouawad.
>>
>>
>>
>
>
> --
> Cordialement.
> Philippe Mouawad.
>
>
>
--
Cordialement.
Philippe Mouawad.