On 11/12/2009 16:51, Harry_ wrote:
I noticed that the response of the Server is HTTP/1.x 302 Found in Browser.

While for JMeter in JMeter Response Header it is

HTTP/1.1 200 OK

Can you see why this is different in jMeter and Browser.

In the sample you show, JMeter is sent a 302 response as well. I suspect that the 302 redirect is correct behaviour, and that the body of the 200 response may give more details of the problem.

Either that your application is doing something strange that we don't understand, or there is a difference between the two requests. If it's the former, then you need to work out what the non-HTTP difference is, and if it's the latter, you have to keep changing JMeter until you have a match...

And I believe that Wireshark is available through the Ubuntu package manager, although I'm a Gentoo user myself, so I can't help with the specifics of installing it...


    Ronan

Regards



Harry_ wrote:
I will do that Ronan. Thanks a lot for your time.

Can you please let me know where I could download wireshark for Ubuntu. I
can see only Mac and Win downloads.

Regards


Ronan Klyne-2 wrote:

I can't spot any more differences. That doesn't mean that there aren't
any, just that we're not seeing them.

I think the only thing to do with this now is to compare a JMeter and
browser request, and change JMeter's test plan until the two requests
are identical. You may have to go as far as wireshark to confirm this...

There are two possible outcomes:
   * You make the requests match closely enough for the web server to
accept
or
   * You discover that there is some extra non-HTTP thing (timing or
something) that your server requires. I think something is really wrong
with your SUT if you have one of these problems...

One more afterthought - it could be that JMeter is submitting the
requests too quickly for your server's database to actually commit -
maybe try a delay between each one?


      Ronan


On 11/12/2009 15:55, Harry_ wrote:
Thanks a ton for looking into this Ronan..

I added this Cookie as User defined Cookie... But still the page is not
getting updated.

Regards


Ronan Klyne-2 wrote:

On 11/12/2009 15:03, Harry_ wrote:

Thanks for the Reply Ronan...

Yes I have already extracted the form ID and used it in the POST
request
but
still it is not working.


I've just noticed that there are no cookies being sent in your example
JMeter request - Perhaps the cookie 'has_js' is being set by client JS,
and checked on the server?

I have no idea why someone might write a program this way, but it could
happen....


     # r


Regards

Ronan Klyne-2 wrote:


The parameter 'form_build_id' inthe POSTed data is different between
the
two requests. Is this value being extracted from the previous page
and
correctly substituted?


        Ronan

On 02/12/2009 20:59, Harry_ wrote:


I checked the headers using "Live HTTP Headers" and in "View Result
Tree".

The difference is in setting Cookie. Is it something why my test is
not
accepting the terms and conditions. If yes how do I set these
cookies
in
jMeter, if it is not doing by itself.


Live HTTP Headers Shows:

http://test/legal_accept/56008/3e787bed9257fd643a45a0f2c25fe1aa



POST /legal_accept/56008/3e787bed9257fd643a45a0f2c25fe1aa HTTP/1.1

Host: test
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.0.15)
Gecko/2009102815 Ubuntu/9.04 (jaunty) Firefox/3.0.15

Accept:
text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8

Accept-Language: en-gb,en;q=0.5

Accept-Encoding: gzip,deflate

Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7

Keep-Alive: 300

Connection: keep-alive

Referer:
http://test/legal_accept/56008/3e787bed9257fd643a45a0f2c25fe1aa

Cookie:
__utma=236072452.573991268.1259585934.1259771130.1259784337.4;
__utmz=236072452.1259585934.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none);
SESSdaebf48ce4666186eb29a7f5b9e90b00=3pfe3c5cfn5di2dbebivfs4at0;
__utmv=236072452.authenticated%20user%2Cadministrator%3A%3A%3A%3A%3A;
has_js=1; __utmc=236072452; _csoot=1259775258852;
_csuid=4ae6d3624bed3faf;
__utmb=236072452.53.10.1259784337; DRUPAL_LOGGED_IN=Y

Content-Type: application/x-www-form-urlencoded

Content-Length: 98

form_build_id=form-9565758b95b12d94f330804f32f13449&form_id=legal_login&legal_accept=on&op=Confirm

HTTP/1.x 302 Found

Date: Wed, 02 Dec 2009 20:47:31 GMT

Server: Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.8e-fips-rhel5
PHP/5.2.9

X-Powered-By: PHP/5.2.9

Cache-Control: no-store, no-cache, must-revalidate, post-check=0,
pre-check=0

Pragma: no-cache

Set-Cookie: DRUPAL_LOGGED_IN=Y; expires=Tue, 01-Dec-2009 20:47:31
GMT;
path=/

Set-Cookie: ns_remember=deleted; expires=Tue, 02-Dec-2008 20:47:31
GMT;
path=/

Set-Cookie: DRUPAL_LOGGED_IN=Y; expires=Sat, 26-Dec-2009 00:20:52
GMT;
path=/

Expires: Sun, 19 Nov 1978 05:00:00 GMT

Last-Modified: Mon, 23 Apr 2010 02:00:32 GMT

Etag: "d41d8cd98f00b204e9800998ecf8427e"

X-Drupal: loggedin

Location: http://test/

Content-Length: 0

Connection: close

Content-Type: text/html; charset=utf-8


----------

View Result Tree Headers Shows:

Sampler Result Tab

Thread Name: Thread Group 1-1
Sample Start: 2009-12-02 20:25:31 GMT
Load time: 518
Latency: 518
Size in bytes: 0
Sample Count: 1
Error Count: 0
Response code: 302
Response message: Found

Response headers:
HTTP/1.1 302 Found
Date: Wed, 02 Dec 2009 20:25:50 GMT
Server: Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.8e-fips-rhel5
PHP/5.2.9
X-Powered-By: PHP/5.2.9
Set-Cookie:
SESSdaebf48ce4666186eb29a7f5b9e90b00=mpaspit0fcl9rmp5r2nv5agtg0;
expires=Fri, 25-Dec-2009 23:59:10 GMT; path=/; domain=.test
Expires: Sun, 19 Nov 1978 05:00:00 GMT
Last-Modified: Mon, 23 Apr 2010 02:00:32 GMT
Cache-Control: post-check=0, pre-check=0
ETag: "d41d8cd98f00b204e9800998ecf8427e"
Location: http://test/
Content-Length: 0
Connection: close
Content-Type: text/html; charset=utf-8


HTTPSampleResult fields:
ContentType: text/html; charset=utf-8
DataEncoding: utf-8
---------------------------------
Request Tab

POST http://test/legal_accept/56005/1c54c8bf3308d9138388b77d7b0911bf

POST data:
form_build_id=form-3b21145374b980b87ef4fd87e64f625a&form_id=legal_login&legal_accept=on&op=Confirm

[no cookies]

Request Headers:
Accept-Language: en-gb,en;q=0.5
Content-Length: 98
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Referer:
http://test/legal_accept/56005/1c54c8bf3308d9138388b77d7b0911bf
Accept-Encoding: gzip,deflate
Keep-Alive: 300
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.0.15)
Gecko/2009102815 Ubuntu/9.04 (jaunty) Firefox/3.0.15
Connection: keep-alive
Content-Type: application/x-www-form-urlencoded
Accept:
text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8







Deepak Shetty wrote:



All of these class of problems are covered by 'Why does Jmeter not
behave
like my browser' covered in
http://wiki.apache.org/jakarta-jmeter/DifferentBehaviour. And all
need
you
to understand how your application behaves(any browser tool like
fiddler/livehttpheaders) v/s what Jmeter is sending(view results
tree).

If i have to guess, your application probably stores the acceptance
as
a
cookie, and the second iteration (for the different user) probably
does
something wrong. perhaps you clear the cookies and dont set it,
perhaps
you
get the earlier cookie, you need to .This is a guess , we dont
know,
check
your application against what you have specified in jmeter
regards
deepak

On Wed, Dec 2, 2009 at 9:07 AM, Harry_<[email protected]>
wrote:




Hi,

I have created a test plan using HTTP Proxy Server recording the
following
sequence.

1. New User Login to System with valid user name and Password.
2. Accepts the terms and conditions (This sends post information
to
server
that user is accepting terms and conditions. This happens only
once.)
3. Now user can navigate various pages of the site which are
accessible
to
login user.

Now when I re-run this test with different new user with different
username/password from csv file, i get the following error for
pages
of
third step.

     Response code: 403
     Response message: Forbidden

First two steps shows success and I have checked that jMeter
during
the
run
sends terms and condition accept params to the server of step2.

But the terms and conditions are still not accepted that is why we
get
the
error on pages of step 3.

Now can anyone point me where could be the problem. Why Post
params
sent
through jMeter for checkboxes is not accepted by the server.

The problem seems to be with check boxes only. Because if I had
already
accepted the terms and conditions, jmeter works fine for every
request.

If this a defect can anyone suggest me a workaround. I have to
work
with
checkboxes quite often, so I am facing this problem everywhere.

Thanks and Regards
--
View this message in context:
http://old.nabble.com/Accept-Terms-and-Conditions-checkbox-not-working-through-jMeter-tp26612532p26612532.html
Sent from the JMeter - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail:
[email protected]







---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]






---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]






---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]






---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to