You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by Ryan <gr...@gmail.com> on 2012/03/05 21:57:06 UTC
Website Login Issue
It's been a while since I've used JMeter and recently started using it
again to test one of our webapps here. It is a pretty standard ASP.Net 4
app, nothing crazy. I implemented a simple test script just to make sure
login works as expected, but I cannot get this thing to work.
The steps are pretty simple:
/login.aspx
/default.aspx
/logout.aspx
/login.aspx
For the first login.aspx call, I'm including two parameters in the POST to
pass the login name and password values that are expected. In my View
Results Tree, this step does include the correct POST data and login
parameters.
However, once it moves to the /default.aspx step, the only response I get
is:
<html><head><title>Object moved</title></head><body>
<h2>Object moved to <a href="/timeout.aspx">here</a>.</h2>
</body></html>
It then adds a step calling the /timeout.aspx page, which outputs the
following response:
<html><head><title>Object moved</title></head><body>
<h2>Object moved to <a href="/login.aspx">here</a>.</h2>
</body></html>
It then calls the /login.aspx page. This is the correct behavior if the
user is not logged in any longer (meaning a specific session value is no
longer valid or has been removed)...it redirects to /timeout.aspx which
then forwards to /login.aspx. The question is why this is happening, as
this is not what happens in the browser.
I have an HTTP Cookie Manager to store the session values, and the session
cookie is showing up in the step request.
I figured I screwed something up so I recorded a test script with the HTTP
Proxy Server and it gave me the exact same steps and results as when I
manually created it, so I'm stuck at this point. I've double-checked the
web site script tutorials on the JMeter site as well as around the web and
it should be working.
Any ideas? Any help would be appreciated.
Re: Website Login Issue
Posted by sebb <se...@gmail.com>.
On 14 March 2012 19:17, Ryan <gr...@gmail.com> wrote:
> Well, the session id should be different since it is a different client
> sending the request. The same thing would happen if you loaded a
> session-aware page in two different browsers, they would each have their
> own http session.
Yes, of course the value of the id will be different for the different sessions.
However, sessionIds are generally just a key which is used to look up
the state of the session in the server.
The server will maintain settings such as when the session started,
what privileges it has, what state it is in - e.g has it logged in
yet?
> The initial loading of the login page is also the same between JMeter and
> the browser. This page does load correctly, the response data contains all
> of the generated content from the login.aspx page.
As I already wrote, the server must be seeing something different
between the two clients, otherwise why is it behaving differently?
I suggest you compare Wireshark sessions for browser and JMeter.
> Browser:
>
> GET /login.aspx HTTP/1.1
> Host: <ip-address>
> User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2)
> Gecko/20100101 Firefox/10.0.2
> Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
> Accept-Language: en-us,en;q=0.5
> Accept-Encoding: gzip, deflate
> Connection: keep-alive
> Cookie: ASP.NET_SessionId=ht0xkz1uekskfqtyvwzclyb0; CurrentLanguage=en-US
>
> JMeter (pulled from Wireshark):
>
> GET /login.aspx HTTP/1.1
> Connection: keep-alive
> User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20100101
> Firefox/10.0.2
> Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
> Accept-Encoding: gzip, deflate
> Accept-Language: en-us,en;q=0.5
> Host: <ip-address>
>
>
>
>
>
>
> On Wed, Mar 14, 2012 at 1:12 PM, sebb <se...@gmail.com> wrote:
>
>> On 14 March 2012 17:55, Ryan <gr...@gmail.com> wrote:
>> > I've double checked the POST request headers and they are exactly the
>> same.
>>
>> The sessionId is different; perhaps it encodes some state that is not
>> the same for the two sessions?
>>
>> If so, there must be a difference in a previous request that led to this.
>>
>> The server only knows what it is given, so if it behaves differently
>> for different clients, the clients must be doing different things.
>>
>> If the earlier requests are identical also, then you will have to
>> start looking at request timing, but it seems very unlikely that the
>> server will depend on that.
>>
>> > Browser:
>> >
>> > POST /login.aspx HTTP/1.1
>> > Host: <ip address>
>> > User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2)
>> > Gecko/20100101 Firefox/10.0.2
>> > Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
>> > Accept-Language: en-us,en;q=0.5
>> > Accept-Encoding: gzip, deflate
>> > Connection: keep-alive
>> > Referer: http://<ip address>/login.aspx
>> > Cookie: ASP.NET_SessionId=ht0xkz1uekskfqtyvwzclyb0; CurrentLanguage=en-US
>> > Content-Type: application/x-www-form-urlencoded
>> >
>> > JMeter (captured with Wireshark):
>> >
>> > POST /login.aspx HTTP/1.1
>> > Connection: keep-alive
>> > User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20100101
>> > Firefox/10.0.2
>> > Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
>> > Accept-Encoding: gzip, deflate
>> > Accept-Language: en-us,en;q=0.5
>> > Cookie: ASP.NET_SessionId=tt03udtituidt5fjahryikz2; CurrentLanguage=en-US
>> > Referer: http://<ip-address>/login.aspx
>> > Host: <ip-address>
>> > Content-Type: application/x-www-form-urlencoded
>> >
>> >
>> >
>> >
>> > On Wed, Mar 14, 2012 at 12:22 PM, karl <ka...@sitestress.eu> wrote:
>> >
>> >> you could compare the Requests from the browser with the requests by
>> >> jmeter with a second jmeter with running proxy
>> >>
>> >> first session: browser -> jmeter-proxy -> server
>> >> = testplan1
>> >>
>> >> second session:
>> >> jmeter1-with-testplan1 -> jmeter2-proxy -> server
>> >>
>> >> jmeter1 must use the jmeter2-proxy, start jmeter1 with
>> >> jmeter.bat -H 127.00.0.1 -P 8012
>> >> and configure jmeter2-proxy listen on port 8012
>> >>
>> >> now, compare the two test
>> >>
>> >> regards
>> >> karl
>> >>
>> >> Am 14.03.2012 17:36, schrieb sebb:
>> >>
>> >>> On 14 March 2012 16:15, Ryan<gr...@gmail.com> wrote:
>> >>>
>> >>>> Does anyone have any ideas on this? We're still having this issue.
>> I've
>> >>>> made sure that the VIEWSTATE is captured, et cetera. Everything seems
>> to
>> >>>> be
>> >>>> in order but something still isn't happy. This is a really simple test
>> >>>> case, so I'm confused as to why it isn't working.
>> >>>>
>> >>> There must be something missing or otherwise wrong in the request(s)
>> >>> you are sending.
>> >>>
>> >>> If you can successfully login using a browser or other client, use a
>> >>> packet analyser such as Wireshark to compare what it sends with what
>> >>> JMeter sends.
>> >>>
>> >>> It could be something a simple as the user agent string - investigate
>> >>> each and every difference until you find the problem.
>> >>>
>> >>> On Wed, Mar 7, 2012 at 5:12 PM, Ryan<gr...@gmail.com> wrote:
>> >>>>
>> >>>> The application doesn't use OAuth, so that does not apply here.
>> Surely
>> >>>>> someone out there has an idea on how to get this to work?
>> >>>>>
>> >>>>>
>> >>>>> On Wed, Mar 7, 2012 at 3:43 PM, Shay Ginsbourg<sginsbourg@gmail.com
>> **
>> >>>>> >wrote:
>> >>>>>
>> >>>>> 1. Should check the possibility of working with -> "JMeter OAuth
>> >>>>>> Sampler".
>> >>>>>>
>> >>>>>> 2. Also, can download 30-days trial free RADVIEW WEBLOAD -> record,
>> >>>>>> replay,
>> >>>>>> auto-correlate, and gain some new insight into your Jmeter script.
>> >>>>>>
>> >>>>>> Good luck!
>> >>>>>> Shay
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>> On Wed, Mar 7, 2012 at 22:15, Ryan<gr...@gmail.com> wrote:
>> >>>>>>
>> >>>>>> I've double checked everything that the browser requests and all
>> >>>>>>> parameters match up with the JMeter http request configuration for
>> the
>> >>>>>>> login action, including the ASP.Net parameters. I'm using JMeter
>> 2.6,
>> >>>>>>>
>> >>>>>> for
>> >>>>>>
>> >>>>>>> the record.
>> >>>>>>>
>> >>>>>>> I've attached an image showing the request configuration, the
>> actual
>> >>>>>>> request contents and the browser's request contents for comparison.
>> >>>>>>>
>> >>>>>>> On Mon, Mar 5, 2012 at 3:09 PM, Deepak Shetty<sh...@gmail.com>
>> >>>>>>>
>> >>>>>> wrote:
>> >>>>>>
>> >>>>>>> your probably not extracting out the dynamic asp.net parameters
>> >>>>>>>> (viewstate
>> >>>>>>>> ,eventvalidation etc)
>> >>>>>>>> otherwise compare what browser sends and receives.
>> >>>>>>>>
>> >>>>>>>> regards
>> >>>>>>>> deepak
>> >>>>>>>>
>> >>>>>>>> On Mon, Mar 5, 2012 at 12:57 PM, Ryan<gr...@gmail.com> wrote:
>> >>>>>>>>
>> >>>>>>>> It's been a while since I've used JMeter and recently started
>> using
>> >>>>>>>>>
>> >>>>>>>> it
>> >>>>>>
>> >>>>>>> again to test one of our webapps here. It is a pretty standard
>> >>>>>>>>>
>> >>>>>>>> ASP.Net 4
>> >>>>>>
>> >>>>>>> app, nothing crazy. I implemented a simple test script just to make
>> >>>>>>>>>
>> >>>>>>>> sure
>> >>>>>>
>> >>>>>>> login works as expected, but I cannot get this thing to work.
>> >>>>>>>>>
>> >>>>>>>>> The steps are pretty simple:
>> >>>>>>>>> /login.aspx
>> >>>>>>>>> /default.aspx
>> >>>>>>>>> /logout.aspx
>> >>>>>>>>> /login.aspx
>> >>>>>>>>>
>> >>>>>>>>> For the first login.aspx call, I'm including two parameters in
>> the
>> >>>>>>>>>
>> >>>>>>>> POST
>> >>>>>>
>> >>>>>>> to
>> >>>>>>>>
>> >>>>>>>>> pass the login name and password values that are expected. In my
>> >>>>>>>>> View
>> >>>>>>>>> Results Tree, this step does include the correct POST data and
>> login
>> >>>>>>>>> parameters.
>> >>>>>>>>>
>> >>>>>>>>> However, once it moves to the /default.aspx step, the only
>> response
>> >>>>>>>>> I
>> >>>>>>>>>
>> >>>>>>>> get
>> >>>>>>>>
>> >>>>>>>>> is:
>> >>>>>>>>>
>> >>>>>>>>> <html><head><title>Object moved</title></head><body>
>> >>>>>>>>> <h2>Object moved to<a href="/timeout.aspx">here</a>.**</h2>
>> >>>>>>>>> </body></html>
>> >>>>>>>>>
>> >>>>>>>>> It then adds a step calling the /timeout.aspx page, which outputs
>> >>>>>>>>> the
>> >>>>>>>>> following response:
>> >>>>>>>>>
>> >>>>>>>>> <html><head><title>Object moved</title></head><body>
>> >>>>>>>>> <h2>Object moved to<a href="/login.aspx">here</a>.</**h2>
>> >>>>>>>>> </body></html>
>> >>>>>>>>>
>> >>>>>>>>> It then calls the /login.aspx page. This is the correct behavior
>> if
>> >>>>>>>>>
>> >>>>>>>> the
>> >>>>>>
>> >>>>>>> user is not logged in any longer (meaning a specific session value
>> >>>>>>>>>
>> >>>>>>>> is no
>> >>>>>>
>> >>>>>>> longer valid or has been removed)...it redirects to /timeout.aspx
>> >>>>>>>>>
>> >>>>>>>> which
>> >>>>>>
>> >>>>>>> then forwards to /login.aspx. The question is why this is
>> happening,
>> >>>>>>>>>
>> >>>>>>>> as
>> >>>>>>
>> >>>>>>> this is not what happens in the browser.
>> >>>>>>>>>
>> >>>>>>>>> I have an HTTP Cookie Manager to store the session values, and
>> the
>> >>>>>>>>>
>> >>>>>>>> session
>> >>>>>>>>
>> >>>>>>>>> cookie is showing up in the step request.
>> >>>>>>>>>
>> >>>>>>>>> I figured I screwed something up so I recorded a test script with
>> >>>>>>>>> the
>> >>>>>>>>>
>> >>>>>>>> HTTP
>> >>>>>>>>
>> >>>>>>>>> Proxy Server and it gave me the exact same steps and results as
>> when
>> >>>>>>>>>
>> >>>>>>>> I
>> >>>>>>
>> >>>>>>> manually created it, so I'm stuck at this point. I've
>> double-checked
>> >>>>>>>>>
>> >>>>>>>> the
>> >>>>>>
>> >>>>>>> web site script tutorials on the JMeter site as well as around the
>> >>>>>>>>>
>> >>>>>>>> web
>> >>>>>>
>> >>>>>>> and
>> >>>>>>>>
>> >>>>>>>>> it should be working.
>> >>>>>>>>>
>> >>>>>>>>> Any ideas? Any help would be appreciated.
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>
>> >>>>>>> ------------------------------**------------------------------**
>> >>>>>>> ---------
>> >>>>>>> To unsubscribe, e-mail: user-unsubscribe@jmeter.**apache.org<
>> user-unsubscribe@jmeter.apache.org>
>> >>>>>>> For additional commands, e-mail: user-help@jmeter.apache.org
>> >>>>>>>
>> >>>>>>>
>> >>>>>>
>> >>>>>> --
>> >>>>>>
>> >>>>>>
>> >>>>>> Regulatory, Medical& Performance Testing Services:
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>> * IEC 62304 Medical Device Software Life Cycle
>> >>>>>>
>> >>>>>> * IEEE 829 Software Test Documentation
>> >>>>>>
>> >>>>>> * ISO 14971 Medical Device Risk Management
>> >>>>>>
>> >>>>>> * FDA 21 CFR Part 11 Software Validation
>> >>>>>>
>> >>>>>> * IEC 60601-1:2005 3rd ED PEMS - Medical Electrical Equipment
>> >>>>>>
>> >>>>>> * End-to-end verification, validation, and testing (VV&T)
>> >>>>>>
>> >>>>>> * High quality service for FDA and CE submissions
>> >>>>>>
>> >>>>>> * Reliable open source free testing tools
>> >>>>>>
>> >>>>>> * Optional functionality and regression testing
>> >>>>>>
>> >>>>>> * Software Performance& Load Testing
>> >>>>>>
>> >>>>>>
>> >>>>>> * Software Testing Advanced Automation
>> >>>>>>
>> >>>>>> * Medical Software Verification& Validation
>> >>>>>>
>> >>>>>> * Medical Device Verification& Validation
>> >>>>>>
>> >>>>>>
>> >>>>>> * Medical Device Regulatory Submission
>> >>>>>>
>> >>>>>> * Organizational Regulatory Qualification
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>> Shay Ginsbourg
>> >>>>>>
>> >>>>>> Regulatory& Testing Affairs Consultant
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>> Formerly QA Manager of LoadRunner at Mercury Interactive
>> >>>>>>
>> >>>>>>
>> >>>>>> M.Sc. cum laude in Bio-Medical Engineering
>> >>>>>>
>> >>>>>> M.Sc. in Mechanical Engineering
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>> Work: 035185873
>> >>>>>>
>> >>>>>> Mobile: 0546690915
>> >>>>>>
>> >>>>>>
>> >>>>>> Email: sginsbourg@gmail.com
>> >>>>>>
>> >>>>>>
>> >>>>>> http://il.linkedin.com/in/**shayginsbourg<
>> http://il.linkedin.com/in/shayginsbourg>
>> >>>>>>
>> >>>>>>
>> >>>>>> WWW.GINSBOURG.COM
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>> Please consider your environmental responsibility before printing
>> this
>> >>>>>> e-mail.
>> >>>>>>
>> >>>>>>
>> >>>>> ------------------------------**------------------------------**
>> >>> ---------
>> >>> To unsubscribe, e-mail: user-unsubscribe@jmeter.**apache.org<
>> user-unsubscribe@jmeter.apache.org>
>> >>> For additional commands, e-mail: user-help@jmeter.apache.org
>> >>>
>> >>>
>> >>>
>> >>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
>> For additional commands, e-mail: user-help@jmeter.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
For additional commands, e-mail: user-help@jmeter.apache.org
Re: Website Login Issue
Posted by Ryan <gr...@gmail.com>.
Well, the session id should be different since it is a different client
sending the request. The same thing would happen if you loaded a
session-aware page in two different browsers, they would each have their
own http session.
The initial loading of the login page is also the same between JMeter and
the browser. This page does load correctly, the response data contains all
of the generated content from the login.aspx page.
Browser:
GET /login.aspx HTTP/1.1
Host: <ip-address>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2)
Gecko/20100101 Firefox/10.0.2
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip, deflate
Connection: keep-alive
Cookie: ASP.NET_SessionId=ht0xkz1uekskfqtyvwzclyb0; CurrentLanguage=en-US
JMeter (pulled from Wireshark):
GET /login.aspx HTTP/1.1
Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20100101
Firefox/10.0.2
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Encoding: gzip, deflate
Accept-Language: en-us,en;q=0.5
Host: <ip-address>
On Wed, Mar 14, 2012 at 1:12 PM, sebb <se...@gmail.com> wrote:
> On 14 March 2012 17:55, Ryan <gr...@gmail.com> wrote:
> > I've double checked the POST request headers and they are exactly the
> same.
>
> The sessionId is different; perhaps it encodes some state that is not
> the same for the two sessions?
>
> If so, there must be a difference in a previous request that led to this.
>
> The server only knows what it is given, so if it behaves differently
> for different clients, the clients must be doing different things.
>
> If the earlier requests are identical also, then you will have to
> start looking at request timing, but it seems very unlikely that the
> server will depend on that.
>
> > Browser:
> >
> > POST /login.aspx HTTP/1.1
> > Host: <ip address>
> > User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2)
> > Gecko/20100101 Firefox/10.0.2
> > Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
> > Accept-Language: en-us,en;q=0.5
> > Accept-Encoding: gzip, deflate
> > Connection: keep-alive
> > Referer: http://<ip address>/login.aspx
> > Cookie: ASP.NET_SessionId=ht0xkz1uekskfqtyvwzclyb0; CurrentLanguage=en-US
> > Content-Type: application/x-www-form-urlencoded
> >
> > JMeter (captured with Wireshark):
> >
> > POST /login.aspx HTTP/1.1
> > Connection: keep-alive
> > User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20100101
> > Firefox/10.0.2
> > Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
> > Accept-Encoding: gzip, deflate
> > Accept-Language: en-us,en;q=0.5
> > Cookie: ASP.NET_SessionId=tt03udtituidt5fjahryikz2; CurrentLanguage=en-US
> > Referer: http://<ip-address>/login.aspx
> > Host: <ip-address>
> > Content-Type: application/x-www-form-urlencoded
> >
> >
> >
> >
> > On Wed, Mar 14, 2012 at 12:22 PM, karl <ka...@sitestress.eu> wrote:
> >
> >> you could compare the Requests from the browser with the requests by
> >> jmeter with a second jmeter with running proxy
> >>
> >> first session: browser -> jmeter-proxy -> server
> >> = testplan1
> >>
> >> second session:
> >> jmeter1-with-testplan1 -> jmeter2-proxy -> server
> >>
> >> jmeter1 must use the jmeter2-proxy, start jmeter1 with
> >> jmeter.bat -H 127.00.0.1 -P 8012
> >> and configure jmeter2-proxy listen on port 8012
> >>
> >> now, compare the two test
> >>
> >> regards
> >> karl
> >>
> >> Am 14.03.2012 17:36, schrieb sebb:
> >>
> >>> On 14 March 2012 16:15, Ryan<gr...@gmail.com> wrote:
> >>>
> >>>> Does anyone have any ideas on this? We're still having this issue.
> I've
> >>>> made sure that the VIEWSTATE is captured, et cetera. Everything seems
> to
> >>>> be
> >>>> in order but something still isn't happy. This is a really simple test
> >>>> case, so I'm confused as to why it isn't working.
> >>>>
> >>> There must be something missing or otherwise wrong in the request(s)
> >>> you are sending.
> >>>
> >>> If you can successfully login using a browser or other client, use a
> >>> packet analyser such as Wireshark to compare what it sends with what
> >>> JMeter sends.
> >>>
> >>> It could be something a simple as the user agent string - investigate
> >>> each and every difference until you find the problem.
> >>>
> >>> On Wed, Mar 7, 2012 at 5:12 PM, Ryan<gr...@gmail.com> wrote:
> >>>>
> >>>> The application doesn't use OAuth, so that does not apply here.
> Surely
> >>>>> someone out there has an idea on how to get this to work?
> >>>>>
> >>>>>
> >>>>> On Wed, Mar 7, 2012 at 3:43 PM, Shay Ginsbourg<sginsbourg@gmail.com
> **
> >>>>> >wrote:
> >>>>>
> >>>>> 1. Should check the possibility of working with -> "JMeter OAuth
> >>>>>> Sampler".
> >>>>>>
> >>>>>> 2. Also, can download 30-days trial free RADVIEW WEBLOAD -> record,
> >>>>>> replay,
> >>>>>> auto-correlate, and gain some new insight into your Jmeter script.
> >>>>>>
> >>>>>> Good luck!
> >>>>>> Shay
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> On Wed, Mar 7, 2012 at 22:15, Ryan<gr...@gmail.com> wrote:
> >>>>>>
> >>>>>> I've double checked everything that the browser requests and all
> >>>>>>> parameters match up with the JMeter http request configuration for
> the
> >>>>>>> login action, including the ASP.Net parameters. I'm using JMeter
> 2.6,
> >>>>>>>
> >>>>>> for
> >>>>>>
> >>>>>>> the record.
> >>>>>>>
> >>>>>>> I've attached an image showing the request configuration, the
> actual
> >>>>>>> request contents and the browser's request contents for comparison.
> >>>>>>>
> >>>>>>> On Mon, Mar 5, 2012 at 3:09 PM, Deepak Shetty<sh...@gmail.com>
> >>>>>>>
> >>>>>> wrote:
> >>>>>>
> >>>>>>> your probably not extracting out the dynamic asp.net parameters
> >>>>>>>> (viewstate
> >>>>>>>> ,eventvalidation etc)
> >>>>>>>> otherwise compare what browser sends and receives.
> >>>>>>>>
> >>>>>>>> regards
> >>>>>>>> deepak
> >>>>>>>>
> >>>>>>>> On Mon, Mar 5, 2012 at 12:57 PM, Ryan<gr...@gmail.com> wrote:
> >>>>>>>>
> >>>>>>>> It's been a while since I've used JMeter and recently started
> using
> >>>>>>>>>
> >>>>>>>> it
> >>>>>>
> >>>>>>> again to test one of our webapps here. It is a pretty standard
> >>>>>>>>>
> >>>>>>>> ASP.Net 4
> >>>>>>
> >>>>>>> app, nothing crazy. I implemented a simple test script just to make
> >>>>>>>>>
> >>>>>>>> sure
> >>>>>>
> >>>>>>> login works as expected, but I cannot get this thing to work.
> >>>>>>>>>
> >>>>>>>>> The steps are pretty simple:
> >>>>>>>>> /login.aspx
> >>>>>>>>> /default.aspx
> >>>>>>>>> /logout.aspx
> >>>>>>>>> /login.aspx
> >>>>>>>>>
> >>>>>>>>> For the first login.aspx call, I'm including two parameters in
> the
> >>>>>>>>>
> >>>>>>>> POST
> >>>>>>
> >>>>>>> to
> >>>>>>>>
> >>>>>>>>> pass the login name and password values that are expected. In my
> >>>>>>>>> View
> >>>>>>>>> Results Tree, this step does include the correct POST data and
> login
> >>>>>>>>> parameters.
> >>>>>>>>>
> >>>>>>>>> However, once it moves to the /default.aspx step, the only
> response
> >>>>>>>>> I
> >>>>>>>>>
> >>>>>>>> get
> >>>>>>>>
> >>>>>>>>> is:
> >>>>>>>>>
> >>>>>>>>> <html><head><title>Object moved</title></head><body>
> >>>>>>>>> <h2>Object moved to<a href="/timeout.aspx">here</a>.**</h2>
> >>>>>>>>> </body></html>
> >>>>>>>>>
> >>>>>>>>> It then adds a step calling the /timeout.aspx page, which outputs
> >>>>>>>>> the
> >>>>>>>>> following response:
> >>>>>>>>>
> >>>>>>>>> <html><head><title>Object moved</title></head><body>
> >>>>>>>>> <h2>Object moved to<a href="/login.aspx">here</a>.</**h2>
> >>>>>>>>> </body></html>
> >>>>>>>>>
> >>>>>>>>> It then calls the /login.aspx page. This is the correct behavior
> if
> >>>>>>>>>
> >>>>>>>> the
> >>>>>>
> >>>>>>> user is not logged in any longer (meaning a specific session value
> >>>>>>>>>
> >>>>>>>> is no
> >>>>>>
> >>>>>>> longer valid or has been removed)...it redirects to /timeout.aspx
> >>>>>>>>>
> >>>>>>>> which
> >>>>>>
> >>>>>>> then forwards to /login.aspx. The question is why this is
> happening,
> >>>>>>>>>
> >>>>>>>> as
> >>>>>>
> >>>>>>> this is not what happens in the browser.
> >>>>>>>>>
> >>>>>>>>> I have an HTTP Cookie Manager to store the session values, and
> the
> >>>>>>>>>
> >>>>>>>> session
> >>>>>>>>
> >>>>>>>>> cookie is showing up in the step request.
> >>>>>>>>>
> >>>>>>>>> I figured I screwed something up so I recorded a test script with
> >>>>>>>>> the
> >>>>>>>>>
> >>>>>>>> HTTP
> >>>>>>>>
> >>>>>>>>> Proxy Server and it gave me the exact same steps and results as
> when
> >>>>>>>>>
> >>>>>>>> I
> >>>>>>
> >>>>>>> manually created it, so I'm stuck at this point. I've
> double-checked
> >>>>>>>>>
> >>>>>>>> the
> >>>>>>
> >>>>>>> web site script tutorials on the JMeter site as well as around the
> >>>>>>>>>
> >>>>>>>> web
> >>>>>>
> >>>>>>> and
> >>>>>>>>
> >>>>>>>>> it should be working.
> >>>>>>>>>
> >>>>>>>>> Any ideas? Any help would be appreciated.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>
> >>>>>>> ------------------------------**------------------------------**
> >>>>>>> ---------
> >>>>>>> To unsubscribe, e-mail: user-unsubscribe@jmeter.**apache.org<
> user-unsubscribe@jmeter.apache.org>
> >>>>>>> For additional commands, e-mail: user-help@jmeter.apache.org
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>> --
> >>>>>>
> >>>>>>
> >>>>>> Regulatory, Medical& Performance Testing Services:
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> * IEC 62304 Medical Device Software Life Cycle
> >>>>>>
> >>>>>> * IEEE 829 Software Test Documentation
> >>>>>>
> >>>>>> * ISO 14971 Medical Device Risk Management
> >>>>>>
> >>>>>> * FDA 21 CFR Part 11 Software Validation
> >>>>>>
> >>>>>> * IEC 60601-1:2005 3rd ED PEMS - Medical Electrical Equipment
> >>>>>>
> >>>>>> * End-to-end verification, validation, and testing (VV&T)
> >>>>>>
> >>>>>> * High quality service for FDA and CE submissions
> >>>>>>
> >>>>>> * Reliable open source free testing tools
> >>>>>>
> >>>>>> * Optional functionality and regression testing
> >>>>>>
> >>>>>> * Software Performance& Load Testing
> >>>>>>
> >>>>>>
> >>>>>> * Software Testing Advanced Automation
> >>>>>>
> >>>>>> * Medical Software Verification& Validation
> >>>>>>
> >>>>>> * Medical Device Verification& Validation
> >>>>>>
> >>>>>>
> >>>>>> * Medical Device Regulatory Submission
> >>>>>>
> >>>>>> * Organizational Regulatory Qualification
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> Shay Ginsbourg
> >>>>>>
> >>>>>> Regulatory& Testing Affairs Consultant
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> Formerly QA Manager of LoadRunner at Mercury Interactive
> >>>>>>
> >>>>>>
> >>>>>> M.Sc. cum laude in Bio-Medical Engineering
> >>>>>>
> >>>>>> M.Sc. in Mechanical Engineering
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> Work: 035185873
> >>>>>>
> >>>>>> Mobile: 0546690915
> >>>>>>
> >>>>>>
> >>>>>> Email: sginsbourg@gmail.com
> >>>>>>
> >>>>>>
> >>>>>> http://il.linkedin.com/in/**shayginsbourg<
> http://il.linkedin.com/in/shayginsbourg>
> >>>>>>
> >>>>>>
> >>>>>> WWW.GINSBOURG.COM
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> Please consider your environmental responsibility before printing
> this
> >>>>>> e-mail.
> >>>>>>
> >>>>>>
> >>>>> ------------------------------**------------------------------**
> >>> ---------
> >>> To unsubscribe, e-mail: user-unsubscribe@jmeter.**apache.org<
> user-unsubscribe@jmeter.apache.org>
> >>> For additional commands, e-mail: user-help@jmeter.apache.org
> >>>
> >>>
> >>>
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> For additional commands, e-mail: user-help@jmeter.apache.org
>
>
Re: Website Login Issue
Posted by sebb <se...@gmail.com>.
On 14 March 2012 17:55, Ryan <gr...@gmail.com> wrote:
> I've double checked the POST request headers and they are exactly the same.
The sessionId is different; perhaps it encodes some state that is not
the same for the two sessions?
If so, there must be a difference in a previous request that led to this.
The server only knows what it is given, so if it behaves differently
for different clients, the clients must be doing different things.
If the earlier requests are identical also, then you will have to
start looking at request timing, but it seems very unlikely that the
server will depend on that.
> Browser:
>
> POST /login.aspx HTTP/1.1
> Host: <ip address>
> User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2)
> Gecko/20100101 Firefox/10.0.2
> Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
> Accept-Language: en-us,en;q=0.5
> Accept-Encoding: gzip, deflate
> Connection: keep-alive
> Referer: http://<ip address>/login.aspx
> Cookie: ASP.NET_SessionId=ht0xkz1uekskfqtyvwzclyb0; CurrentLanguage=en-US
> Content-Type: application/x-www-form-urlencoded
>
> JMeter (captured with Wireshark):
>
> POST /login.aspx HTTP/1.1
> Connection: keep-alive
> User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20100101
> Firefox/10.0.2
> Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
> Accept-Encoding: gzip, deflate
> Accept-Language: en-us,en;q=0.5
> Cookie: ASP.NET_SessionId=tt03udtituidt5fjahryikz2; CurrentLanguage=en-US
> Referer: http://<ip-address>/login.aspx
> Host: <ip-address>
> Content-Type: application/x-www-form-urlencoded
>
>
>
>
> On Wed, Mar 14, 2012 at 12:22 PM, karl <ka...@sitestress.eu> wrote:
>
>> you could compare the Requests from the browser with the requests by
>> jmeter with a second jmeter with running proxy
>>
>> first session: browser -> jmeter-proxy -> server
>> = testplan1
>>
>> second session:
>> jmeter1-with-testplan1 -> jmeter2-proxy -> server
>>
>> jmeter1 must use the jmeter2-proxy, start jmeter1 with
>> jmeter.bat -H 127.00.0.1 -P 8012
>> and configure jmeter2-proxy listen on port 8012
>>
>> now, compare the two test
>>
>> regards
>> karl
>>
>> Am 14.03.2012 17:36, schrieb sebb:
>>
>>> On 14 March 2012 16:15, Ryan<gr...@gmail.com> wrote:
>>>
>>>> Does anyone have any ideas on this? We're still having this issue. I've
>>>> made sure that the VIEWSTATE is captured, et cetera. Everything seems to
>>>> be
>>>> in order but something still isn't happy. This is a really simple test
>>>> case, so I'm confused as to why it isn't working.
>>>>
>>> There must be something missing or otherwise wrong in the request(s)
>>> you are sending.
>>>
>>> If you can successfully login using a browser or other client, use a
>>> packet analyser such as Wireshark to compare what it sends with what
>>> JMeter sends.
>>>
>>> It could be something a simple as the user agent string - investigate
>>> each and every difference until you find the problem.
>>>
>>> On Wed, Mar 7, 2012 at 5:12 PM, Ryan<gr...@gmail.com> wrote:
>>>>
>>>> The application doesn't use OAuth, so that does not apply here. Surely
>>>>> someone out there has an idea on how to get this to work?
>>>>>
>>>>>
>>>>> On Wed, Mar 7, 2012 at 3:43 PM, Shay Ginsbourg<sginsbourg@gmail.com**
>>>>> >wrote:
>>>>>
>>>>> 1. Should check the possibility of working with -> "JMeter OAuth
>>>>>> Sampler".
>>>>>>
>>>>>> 2. Also, can download 30-days trial free RADVIEW WEBLOAD -> record,
>>>>>> replay,
>>>>>> auto-correlate, and gain some new insight into your Jmeter script.
>>>>>>
>>>>>> Good luck!
>>>>>> Shay
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Wed, Mar 7, 2012 at 22:15, Ryan<gr...@gmail.com> wrote:
>>>>>>
>>>>>> I've double checked everything that the browser requests and all
>>>>>>> parameters match up with the JMeter http request configuration for the
>>>>>>> login action, including the ASP.Net parameters. I'm using JMeter 2.6,
>>>>>>>
>>>>>> for
>>>>>>
>>>>>>> the record.
>>>>>>>
>>>>>>> I've attached an image showing the request configuration, the actual
>>>>>>> request contents and the browser's request contents for comparison.
>>>>>>>
>>>>>>> On Mon, Mar 5, 2012 at 3:09 PM, Deepak Shetty<sh...@gmail.com>
>>>>>>>
>>>>>> wrote:
>>>>>>
>>>>>>> your probably not extracting out the dynamic asp.net parameters
>>>>>>>> (viewstate
>>>>>>>> ,eventvalidation etc)
>>>>>>>> otherwise compare what browser sends and receives.
>>>>>>>>
>>>>>>>> regards
>>>>>>>> deepak
>>>>>>>>
>>>>>>>> On Mon, Mar 5, 2012 at 12:57 PM, Ryan<gr...@gmail.com> wrote:
>>>>>>>>
>>>>>>>> It's been a while since I've used JMeter and recently started using
>>>>>>>>>
>>>>>>>> it
>>>>>>
>>>>>>> again to test one of our webapps here. It is a pretty standard
>>>>>>>>>
>>>>>>>> ASP.Net 4
>>>>>>
>>>>>>> app, nothing crazy. I implemented a simple test script just to make
>>>>>>>>>
>>>>>>>> sure
>>>>>>
>>>>>>> login works as expected, but I cannot get this thing to work.
>>>>>>>>>
>>>>>>>>> The steps are pretty simple:
>>>>>>>>> /login.aspx
>>>>>>>>> /default.aspx
>>>>>>>>> /logout.aspx
>>>>>>>>> /login.aspx
>>>>>>>>>
>>>>>>>>> For the first login.aspx call, I'm including two parameters in the
>>>>>>>>>
>>>>>>>> POST
>>>>>>
>>>>>>> to
>>>>>>>>
>>>>>>>>> pass the login name and password values that are expected. In my
>>>>>>>>> View
>>>>>>>>> Results Tree, this step does include the correct POST data and login
>>>>>>>>> parameters.
>>>>>>>>>
>>>>>>>>> However, once it moves to the /default.aspx step, the only response
>>>>>>>>> I
>>>>>>>>>
>>>>>>>> get
>>>>>>>>
>>>>>>>>> is:
>>>>>>>>>
>>>>>>>>> <html><head><title>Object moved</title></head><body>
>>>>>>>>> <h2>Object moved to<a href="/timeout.aspx">here</a>.**</h2>
>>>>>>>>> </body></html>
>>>>>>>>>
>>>>>>>>> It then adds a step calling the /timeout.aspx page, which outputs
>>>>>>>>> the
>>>>>>>>> following response:
>>>>>>>>>
>>>>>>>>> <html><head><title>Object moved</title></head><body>
>>>>>>>>> <h2>Object moved to<a href="/login.aspx">here</a>.</**h2>
>>>>>>>>> </body></html>
>>>>>>>>>
>>>>>>>>> It then calls the /login.aspx page. This is the correct behavior if
>>>>>>>>>
>>>>>>>> the
>>>>>>
>>>>>>> user is not logged in any longer (meaning a specific session value
>>>>>>>>>
>>>>>>>> is no
>>>>>>
>>>>>>> longer valid or has been removed)...it redirects to /timeout.aspx
>>>>>>>>>
>>>>>>>> which
>>>>>>
>>>>>>> then forwards to /login.aspx. The question is why this is happening,
>>>>>>>>>
>>>>>>>> as
>>>>>>
>>>>>>> this is not what happens in the browser.
>>>>>>>>>
>>>>>>>>> I have an HTTP Cookie Manager to store the session values, and the
>>>>>>>>>
>>>>>>>> session
>>>>>>>>
>>>>>>>>> cookie is showing up in the step request.
>>>>>>>>>
>>>>>>>>> I figured I screwed something up so I recorded a test script with
>>>>>>>>> the
>>>>>>>>>
>>>>>>>> HTTP
>>>>>>>>
>>>>>>>>> Proxy Server and it gave me the exact same steps and results as when
>>>>>>>>>
>>>>>>>> I
>>>>>>
>>>>>>> manually created it, so I'm stuck at this point. I've double-checked
>>>>>>>>>
>>>>>>>> the
>>>>>>
>>>>>>> web site script tutorials on the JMeter site as well as around the
>>>>>>>>>
>>>>>>>> web
>>>>>>
>>>>>>> and
>>>>>>>>
>>>>>>>>> it should be working.
>>>>>>>>>
>>>>>>>>> Any ideas? Any help would be appreciated.
>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>>> ------------------------------**------------------------------**
>>>>>>> ---------
>>>>>>> To unsubscribe, e-mail: user-unsubscribe@jmeter.**apache.org<us...@jmeter.apache.org>
>>>>>>> For additional commands, e-mail: user-help@jmeter.apache.org
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>>
>>>>>> Regulatory, Medical& Performance Testing Services:
>>>>>>
>>>>>>
>>>>>>
>>>>>> * IEC 62304 Medical Device Software Life Cycle
>>>>>>
>>>>>> * IEEE 829 Software Test Documentation
>>>>>>
>>>>>> * ISO 14971 Medical Device Risk Management
>>>>>>
>>>>>> * FDA 21 CFR Part 11 Software Validation
>>>>>>
>>>>>> * IEC 60601-1:2005 3rd ED PEMS - Medical Electrical Equipment
>>>>>>
>>>>>> * End-to-end verification, validation, and testing (VV&T)
>>>>>>
>>>>>> * High quality service for FDA and CE submissions
>>>>>>
>>>>>> * Reliable open source free testing tools
>>>>>>
>>>>>> * Optional functionality and regression testing
>>>>>>
>>>>>> * Software Performance& Load Testing
>>>>>>
>>>>>>
>>>>>> * Software Testing Advanced Automation
>>>>>>
>>>>>> * Medical Software Verification& Validation
>>>>>>
>>>>>> * Medical Device Verification& Validation
>>>>>>
>>>>>>
>>>>>> * Medical Device Regulatory Submission
>>>>>>
>>>>>> * Organizational Regulatory Qualification
>>>>>>
>>>>>>
>>>>>>
>>>>>> Shay Ginsbourg
>>>>>>
>>>>>> Regulatory& Testing Affairs Consultant
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Formerly QA Manager of LoadRunner at Mercury Interactive
>>>>>>
>>>>>>
>>>>>> M.Sc. cum laude in Bio-Medical Engineering
>>>>>>
>>>>>> M.Sc. in Mechanical Engineering
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Work: 035185873
>>>>>>
>>>>>> Mobile: 0546690915
>>>>>>
>>>>>>
>>>>>> Email: sginsbourg@gmail.com
>>>>>>
>>>>>>
>>>>>> http://il.linkedin.com/in/**shayginsbourg<http://il.linkedin.com/in/shayginsbourg>
>>>>>>
>>>>>>
>>>>>> WWW.GINSBOURG.COM
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Please consider your environmental responsibility before printing this
>>>>>> e-mail.
>>>>>>
>>>>>>
>>>>> ------------------------------**------------------------------**
>>> ---------
>>> To unsubscribe, e-mail: user-unsubscribe@jmeter.**apache.org<us...@jmeter.apache.org>
>>> For additional commands, e-mail: user-help@jmeter.apache.org
>>>
>>>
>>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
For additional commands, e-mail: user-help@jmeter.apache.org
Re: Website Login Issue
Posted by Ryan <gr...@gmail.com>.
I've double checked the POST request headers and they are exactly the same.
Browser:
POST /login.aspx HTTP/1.1
Host: <ip address>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2)
Gecko/20100101 Firefox/10.0.2
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip, deflate
Connection: keep-alive
Referer: http://<ip address>/login.aspx
Cookie: ASP.NET_SessionId=ht0xkz1uekskfqtyvwzclyb0; CurrentLanguage=en-US
Content-Type: application/x-www-form-urlencoded
JMeter (captured with Wireshark):
POST /login.aspx HTTP/1.1
Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20100101
Firefox/10.0.2
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Encoding: gzip, deflate
Accept-Language: en-us,en;q=0.5
Cookie: ASP.NET_SessionId=tt03udtituidt5fjahryikz2; CurrentLanguage=en-US
Referer: http://<ip-address>/login.aspx
Host: <ip-address>
Content-Type: application/x-www-form-urlencoded
On Wed, Mar 14, 2012 at 12:22 PM, karl <ka...@sitestress.eu> wrote:
> you could compare the Requests from the browser with the requests by
> jmeter with a second jmeter with running proxy
>
> first session: browser -> jmeter-proxy -> server
> = testplan1
>
> second session:
> jmeter1-with-testplan1 -> jmeter2-proxy -> server
>
> jmeter1 must use the jmeter2-proxy, start jmeter1 with
> jmeter.bat -H 127.00.0.1 -P 8012
> and configure jmeter2-proxy listen on port 8012
>
> now, compare the two test
>
> regards
> karl
>
> Am 14.03.2012 17:36, schrieb sebb:
>
>> On 14 March 2012 16:15, Ryan<gr...@gmail.com> wrote:
>>
>>> Does anyone have any ideas on this? We're still having this issue. I've
>>> made sure that the VIEWSTATE is captured, et cetera. Everything seems to
>>> be
>>> in order but something still isn't happy. This is a really simple test
>>> case, so I'm confused as to why it isn't working.
>>>
>> There must be something missing or otherwise wrong in the request(s)
>> you are sending.
>>
>> If you can successfully login using a browser or other client, use a
>> packet analyser such as Wireshark to compare what it sends with what
>> JMeter sends.
>>
>> It could be something a simple as the user agent string - investigate
>> each and every difference until you find the problem.
>>
>> On Wed, Mar 7, 2012 at 5:12 PM, Ryan<gr...@gmail.com> wrote:
>>>
>>> The application doesn't use OAuth, so that does not apply here. Surely
>>>> someone out there has an idea on how to get this to work?
>>>>
>>>>
>>>> On Wed, Mar 7, 2012 at 3:43 PM, Shay Ginsbourg<sginsbourg@gmail.com**
>>>> >wrote:
>>>>
>>>> 1. Should check the possibility of working with -> "JMeter OAuth
>>>>> Sampler".
>>>>>
>>>>> 2. Also, can download 30-days trial free RADVIEW WEBLOAD -> record,
>>>>> replay,
>>>>> auto-correlate, and gain some new insight into your Jmeter script.
>>>>>
>>>>> Good luck!
>>>>> Shay
>>>>>
>>>>>
>>>>>
>>>>> On Wed, Mar 7, 2012 at 22:15, Ryan<gr...@gmail.com> wrote:
>>>>>
>>>>> I've double checked everything that the browser requests and all
>>>>>> parameters match up with the JMeter http request configuration for the
>>>>>> login action, including the ASP.Net parameters. I'm using JMeter 2.6,
>>>>>>
>>>>> for
>>>>>
>>>>>> the record.
>>>>>>
>>>>>> I've attached an image showing the request configuration, the actual
>>>>>> request contents and the browser's request contents for comparison.
>>>>>>
>>>>>> On Mon, Mar 5, 2012 at 3:09 PM, Deepak Shetty<sh...@gmail.com>
>>>>>>
>>>>> wrote:
>>>>>
>>>>>> your probably not extracting out the dynamic asp.net parameters
>>>>>>> (viewstate
>>>>>>> ,eventvalidation etc)
>>>>>>> otherwise compare what browser sends and receives.
>>>>>>>
>>>>>>> regards
>>>>>>> deepak
>>>>>>>
>>>>>>> On Mon, Mar 5, 2012 at 12:57 PM, Ryan<gr...@gmail.com> wrote:
>>>>>>>
>>>>>>> It's been a while since I've used JMeter and recently started using
>>>>>>>>
>>>>>>> it
>>>>>
>>>>>> again to test one of our webapps here. It is a pretty standard
>>>>>>>>
>>>>>>> ASP.Net 4
>>>>>
>>>>>> app, nothing crazy. I implemented a simple test script just to make
>>>>>>>>
>>>>>>> sure
>>>>>
>>>>>> login works as expected, but I cannot get this thing to work.
>>>>>>>>
>>>>>>>> The steps are pretty simple:
>>>>>>>> /login.aspx
>>>>>>>> /default.aspx
>>>>>>>> /logout.aspx
>>>>>>>> /login.aspx
>>>>>>>>
>>>>>>>> For the first login.aspx call, I'm including two parameters in the
>>>>>>>>
>>>>>>> POST
>>>>>
>>>>>> to
>>>>>>>
>>>>>>>> pass the login name and password values that are expected. In my
>>>>>>>> View
>>>>>>>> Results Tree, this step does include the correct POST data and login
>>>>>>>> parameters.
>>>>>>>>
>>>>>>>> However, once it moves to the /default.aspx step, the only response
>>>>>>>> I
>>>>>>>>
>>>>>>> get
>>>>>>>
>>>>>>>> is:
>>>>>>>>
>>>>>>>> <html><head><title>Object moved</title></head><body>
>>>>>>>> <h2>Object moved to<a href="/timeout.aspx">here</a>.**</h2>
>>>>>>>> </body></html>
>>>>>>>>
>>>>>>>> It then adds a step calling the /timeout.aspx page, which outputs
>>>>>>>> the
>>>>>>>> following response:
>>>>>>>>
>>>>>>>> <html><head><title>Object moved</title></head><body>
>>>>>>>> <h2>Object moved to<a href="/login.aspx">here</a>.</**h2>
>>>>>>>> </body></html>
>>>>>>>>
>>>>>>>> It then calls the /login.aspx page. This is the correct behavior if
>>>>>>>>
>>>>>>> the
>>>>>
>>>>>> user is not logged in any longer (meaning a specific session value
>>>>>>>>
>>>>>>> is no
>>>>>
>>>>>> longer valid or has been removed)...it redirects to /timeout.aspx
>>>>>>>>
>>>>>>> which
>>>>>
>>>>>> then forwards to /login.aspx. The question is why this is happening,
>>>>>>>>
>>>>>>> as
>>>>>
>>>>>> this is not what happens in the browser.
>>>>>>>>
>>>>>>>> I have an HTTP Cookie Manager to store the session values, and the
>>>>>>>>
>>>>>>> session
>>>>>>>
>>>>>>>> cookie is showing up in the step request.
>>>>>>>>
>>>>>>>> I figured I screwed something up so I recorded a test script with
>>>>>>>> the
>>>>>>>>
>>>>>>> HTTP
>>>>>>>
>>>>>>>> Proxy Server and it gave me the exact same steps and results as when
>>>>>>>>
>>>>>>> I
>>>>>
>>>>>> manually created it, so I'm stuck at this point. I've double-checked
>>>>>>>>
>>>>>>> the
>>>>>
>>>>>> web site script tutorials on the JMeter site as well as around the
>>>>>>>>
>>>>>>> web
>>>>>
>>>>>> and
>>>>>>>
>>>>>>>> it should be working.
>>>>>>>>
>>>>>>>> Any ideas? Any help would be appreciated.
>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>> ------------------------------**------------------------------**
>>>>>> ---------
>>>>>> To unsubscribe, e-mail: user-unsubscribe@jmeter.**apache.org<us...@jmeter.apache.org>
>>>>>> For additional commands, e-mail: user-help@jmeter.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>> --
>>>>>
>>>>>
>>>>> Regulatory, Medical& Performance Testing Services:
>>>>>
>>>>>
>>>>>
>>>>> * IEC 62304 Medical Device Software Life Cycle
>>>>>
>>>>> * IEEE 829 Software Test Documentation
>>>>>
>>>>> * ISO 14971 Medical Device Risk Management
>>>>>
>>>>> * FDA 21 CFR Part 11 Software Validation
>>>>>
>>>>> * IEC 60601-1:2005 3rd ED PEMS - Medical Electrical Equipment
>>>>>
>>>>> * End-to-end verification, validation, and testing (VV&T)
>>>>>
>>>>> * High quality service for FDA and CE submissions
>>>>>
>>>>> * Reliable open source free testing tools
>>>>>
>>>>> * Optional functionality and regression testing
>>>>>
>>>>> * Software Performance& Load Testing
>>>>>
>>>>>
>>>>> * Software Testing Advanced Automation
>>>>>
>>>>> * Medical Software Verification& Validation
>>>>>
>>>>> * Medical Device Verification& Validation
>>>>>
>>>>>
>>>>> * Medical Device Regulatory Submission
>>>>>
>>>>> * Organizational Regulatory Qualification
>>>>>
>>>>>
>>>>>
>>>>> Shay Ginsbourg
>>>>>
>>>>> Regulatory& Testing Affairs Consultant
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Formerly QA Manager of LoadRunner at Mercury Interactive
>>>>>
>>>>>
>>>>> M.Sc. cum laude in Bio-Medical Engineering
>>>>>
>>>>> M.Sc. in Mechanical Engineering
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Work: 035185873
>>>>>
>>>>> Mobile: 0546690915
>>>>>
>>>>>
>>>>> Email: sginsbourg@gmail.com
>>>>>
>>>>>
>>>>> http://il.linkedin.com/in/**shayginsbourg<http://il.linkedin.com/in/shayginsbourg>
>>>>>
>>>>>
>>>>> WWW.GINSBOURG.COM
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Please consider your environmental responsibility before printing this
>>>>> e-mail.
>>>>>
>>>>>
>>>> ------------------------------**------------------------------**
>> ---------
>> To unsubscribe, e-mail: user-unsubscribe@jmeter.**apache.org<us...@jmeter.apache.org>
>> For additional commands, e-mail: user-help@jmeter.apache.org
>>
>>
>>
>
Re: Website Login Issue
Posted by karl <ka...@sitestress.eu>.
you could compare the Requests from the browser with the requests by
jmeter with a second jmeter with running proxy
first session: browser -> jmeter-proxy -> server
= testplan1
second session:
jmeter1-with-testplan1 -> jmeter2-proxy -> server
jmeter1 must use the jmeter2-proxy, start jmeter1 with
jmeter.bat -H 127.00.0.1 -P 8012
and configure jmeter2-proxy listen on port 8012
now, compare the two test
regards
karl
Am 14.03.2012 17:36, schrieb sebb:
> On 14 March 2012 16:15, Ryan<gr...@gmail.com> wrote:
>> Does anyone have any ideas on this? We're still having this issue. I've
>> made sure that the VIEWSTATE is captured, et cetera. Everything seems to be
>> in order but something still isn't happy. This is a really simple test
>> case, so I'm confused as to why it isn't working.
> There must be something missing or otherwise wrong in the request(s)
> you are sending.
>
> If you can successfully login using a browser or other client, use a
> packet analyser such as Wireshark to compare what it sends with what
> JMeter sends.
>
> It could be something a simple as the user agent string - investigate
> each and every difference until you find the problem.
>
>> On Wed, Mar 7, 2012 at 5:12 PM, Ryan<gr...@gmail.com> wrote:
>>
>>> The application doesn't use OAuth, so that does not apply here. Surely
>>> someone out there has an idea on how to get this to work?
>>>
>>>
>>> On Wed, Mar 7, 2012 at 3:43 PM, Shay Ginsbourg<sg...@gmail.com>wrote:
>>>
>>>> 1. Should check the possibility of working with -> "JMeter OAuth Sampler".
>>>>
>>>> 2. Also, can download 30-days trial free RADVIEW WEBLOAD -> record,
>>>> replay,
>>>> auto-correlate, and gain some new insight into your Jmeter script.
>>>>
>>>> Good luck!
>>>> Shay
>>>>
>>>>
>>>>
>>>> On Wed, Mar 7, 2012 at 22:15, Ryan<gr...@gmail.com> wrote:
>>>>
>>>>> I've double checked everything that the browser requests and all
>>>>> parameters match up with the JMeter http request configuration for the
>>>>> login action, including the ASP.Net parameters. I'm using JMeter 2.6,
>>>> for
>>>>> the record.
>>>>>
>>>>> I've attached an image showing the request configuration, the actual
>>>>> request contents and the browser's request contents for comparison.
>>>>>
>>>>> On Mon, Mar 5, 2012 at 3:09 PM, Deepak Shetty<sh...@gmail.com>
>>>> wrote:
>>>>>> your probably not extracting out the dynamic asp.net parameters
>>>>>> (viewstate
>>>>>> ,eventvalidation etc)
>>>>>> otherwise compare what browser sends and receives.
>>>>>>
>>>>>> regards
>>>>>> deepak
>>>>>>
>>>>>> On Mon, Mar 5, 2012 at 12:57 PM, Ryan<gr...@gmail.com> wrote:
>>>>>>
>>>>>>> It's been a while since I've used JMeter and recently started using
>>>> it
>>>>>>> again to test one of our webapps here. It is a pretty standard
>>>> ASP.Net 4
>>>>>>> app, nothing crazy. I implemented a simple test script just to make
>>>> sure
>>>>>>> login works as expected, but I cannot get this thing to work.
>>>>>>>
>>>>>>> The steps are pretty simple:
>>>>>>> /login.aspx
>>>>>>> /default.aspx
>>>>>>> /logout.aspx
>>>>>>> /login.aspx
>>>>>>>
>>>>>>> For the first login.aspx call, I'm including two parameters in the
>>>> POST
>>>>>> to
>>>>>>> pass the login name and password values that are expected. In my View
>>>>>>> Results Tree, this step does include the correct POST data and login
>>>>>>> parameters.
>>>>>>>
>>>>>>> However, once it moves to the /default.aspx step, the only response I
>>>>>> get
>>>>>>> is:
>>>>>>>
>>>>>>> <html><head><title>Object moved</title></head><body>
>>>>>>> <h2>Object moved to<a href="/timeout.aspx">here</a>.</h2>
>>>>>>> </body></html>
>>>>>>>
>>>>>>> It then adds a step calling the /timeout.aspx page, which outputs the
>>>>>>> following response:
>>>>>>>
>>>>>>> <html><head><title>Object moved</title></head><body>
>>>>>>> <h2>Object moved to<a href="/login.aspx">here</a>.</h2>
>>>>>>> </body></html>
>>>>>>>
>>>>>>> It then calls the /login.aspx page. This is the correct behavior if
>>>> the
>>>>>>> user is not logged in any longer (meaning a specific session value
>>>> is no
>>>>>>> longer valid or has been removed)...it redirects to /timeout.aspx
>>>> which
>>>>>>> then forwards to /login.aspx. The question is why this is happening,
>>>> as
>>>>>>> this is not what happens in the browser.
>>>>>>>
>>>>>>> I have an HTTP Cookie Manager to store the session values, and the
>>>>>> session
>>>>>>> cookie is showing up in the step request.
>>>>>>>
>>>>>>> I figured I screwed something up so I recorded a test script with the
>>>>>> HTTP
>>>>>>> Proxy Server and it gave me the exact same steps and results as when
>>>> I
>>>>>>> manually created it, so I'm stuck at this point. I've double-checked
>>>> the
>>>>>>> web site script tutorials on the JMeter site as well as around the
>>>> web
>>>>>> and
>>>>>>> it should be working.
>>>>>>>
>>>>>>> Any ideas? Any help would be appreciated.
>>>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
>>>>> For additional commands, e-mail: user-help@jmeter.apache.org
>>>>>
>>>>
>>>>
>>>> --
>>>>
>>>>
>>>> Regulatory, Medical& Performance Testing Services:
>>>>
>>>>
>>>> * IEC 62304 Medical Device Software Life Cycle
>>>>
>>>> * IEEE 829 Software Test Documentation
>>>>
>>>> * ISO 14971 Medical Device Risk Management
>>>>
>>>> * FDA 21 CFR Part 11 Software Validation
>>>>
>>>> * IEC 60601-1:2005 3rd ED PEMS - Medical Electrical Equipment
>>>>
>>>> * End-to-end verification, validation, and testing (VV&T)
>>>>
>>>> * High quality service for FDA and CE submissions
>>>>
>>>> * Reliable open source free testing tools
>>>>
>>>> * Optional functionality and regression testing
>>>>
>>>> * Software Performance& Load Testing
>>>>
>>>> * Software Testing Advanced Automation
>>>>
>>>> * Medical Software Verification& Validation
>>>>
>>>> * Medical Device Verification& Validation
>>>>
>>>> * Medical Device Regulatory Submission
>>>>
>>>> * Organizational Regulatory Qualification
>>>>
>>>>
>>>>
>>>> Shay Ginsbourg
>>>>
>>>> Regulatory& Testing Affairs Consultant
>>>>
>>>>
>>>>
>>>> Formerly QA Manager of LoadRunner at Mercury Interactive
>>>>
>>>>
>>>> M.Sc. cum laude in Bio-Medical Engineering
>>>>
>>>> M.Sc. in Mechanical Engineering
>>>>
>>>>
>>>>
>>>>
>>>> Work: 035185873
>>>>
>>>> Mobile: 0546690915
>>>>
>>>>
>>>> Email: sginsbourg@gmail.com
>>>>
>>>>
>>>> http://il.linkedin.com/in/shayginsbourg
>>>>
>>>>
>>>> WWW.GINSBOURG.COM
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Please consider your environmental responsibility before printing this
>>>> e-mail.
>>>>
>>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> For additional commands, e-mail: user-help@jmeter.apache.org
>
>
Re: Website Login Issue
Posted by sebb <se...@gmail.com>.
On 14 March 2012 16:15, Ryan <gr...@gmail.com> wrote:
> Does anyone have any ideas on this? We're still having this issue. I've
> made sure that the VIEWSTATE is captured, et cetera. Everything seems to be
> in order but something still isn't happy. This is a really simple test
> case, so I'm confused as to why it isn't working.
There must be something missing or otherwise wrong in the request(s)
you are sending.
If you can successfully login using a browser or other client, use a
packet analyser such as Wireshark to compare what it sends with what
JMeter sends.
It could be something a simple as the user agent string - investigate
each and every difference until you find the problem.
> On Wed, Mar 7, 2012 at 5:12 PM, Ryan <gr...@gmail.com> wrote:
>
>> The application doesn't use OAuth, so that does not apply here. Surely
>> someone out there has an idea on how to get this to work?
>>
>>
>> On Wed, Mar 7, 2012 at 3:43 PM, Shay Ginsbourg <sg...@gmail.com>wrote:
>>
>>> 1. Should check the possibility of working with -> "JMeter OAuth Sampler".
>>>
>>> 2. Also, can download 30-days trial free RADVIEW WEBLOAD -> record,
>>> replay,
>>> auto-correlate, and gain some new insight into your Jmeter script.
>>>
>>> Good luck!
>>> Shay
>>>
>>>
>>>
>>> On Wed, Mar 7, 2012 at 22:15, Ryan <gr...@gmail.com> wrote:
>>>
>>> > I've double checked everything that the browser requests and all
>>> > parameters match up with the JMeter http request configuration for the
>>> > login action, including the ASP.Net parameters. I'm using JMeter 2.6,
>>> for
>>> > the record.
>>> >
>>> > I've attached an image showing the request configuration, the actual
>>> > request contents and the browser's request contents for comparison.
>>> >
>>> > On Mon, Mar 5, 2012 at 3:09 PM, Deepak Shetty <sh...@gmail.com>
>>> wrote:
>>> >
>>> >> your probably not extracting out the dynamic asp.net parameters
>>> >> (viewstate
>>> >> ,eventvalidation etc)
>>> >> otherwise compare what browser sends and receives.
>>> >>
>>> >> regards
>>> >> deepak
>>> >>
>>> >> On Mon, Mar 5, 2012 at 12:57 PM, Ryan <gr...@gmail.com> wrote:
>>> >>
>>> >> > It's been a while since I've used JMeter and recently started using
>>> it
>>> >> > again to test one of our webapps here. It is a pretty standard
>>> ASP.Net 4
>>> >> > app, nothing crazy. I implemented a simple test script just to make
>>> sure
>>> >> > login works as expected, but I cannot get this thing to work.
>>> >> >
>>> >> > The steps are pretty simple:
>>> >> > /login.aspx
>>> >> > /default.aspx
>>> >> > /logout.aspx
>>> >> > /login.aspx
>>> >> >
>>> >> > For the first login.aspx call, I'm including two parameters in the
>>> POST
>>> >> to
>>> >> > pass the login name and password values that are expected. In my View
>>> >> > Results Tree, this step does include the correct POST data and login
>>> >> > parameters.
>>> >> >
>>> >> > However, once it moves to the /default.aspx step, the only response I
>>> >> get
>>> >> > is:
>>> >> >
>>> >> > <html><head><title>Object moved</title></head><body>
>>> >> > <h2>Object moved to <a href="/timeout.aspx">here</a>.</h2>
>>> >> > </body></html>
>>> >> >
>>> >> > It then adds a step calling the /timeout.aspx page, which outputs the
>>> >> > following response:
>>> >> >
>>> >> > <html><head><title>Object moved</title></head><body>
>>> >> > <h2>Object moved to <a href="/login.aspx">here</a>.</h2>
>>> >> > </body></html>
>>> >> >
>>> >> > It then calls the /login.aspx page. This is the correct behavior if
>>> the
>>> >> > user is not logged in any longer (meaning a specific session value
>>> is no
>>> >> > longer valid or has been removed)...it redirects to /timeout.aspx
>>> which
>>> >> > then forwards to /login.aspx. The question is why this is happening,
>>> as
>>> >> > this is not what happens in the browser.
>>> >> >
>>> >> > I have an HTTP Cookie Manager to store the session values, and the
>>> >> session
>>> >> > cookie is showing up in the step request.
>>> >> >
>>> >> > I figured I screwed something up so I recorded a test script with the
>>> >> HTTP
>>> >> > Proxy Server and it gave me the exact same steps and results as when
>>> I
>>> >> > manually created it, so I'm stuck at this point. I've double-checked
>>> the
>>> >> > web site script tutorials on the JMeter site as well as around the
>>> web
>>> >> and
>>> >> > it should be working.
>>> >> >
>>> >> > Any ideas? Any help would be appreciated.
>>> >> >
>>> >>
>>> >
>>> >
>>> >
>>> > ---------------------------------------------------------------------
>>> > To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
>>> > For additional commands, e-mail: user-help@jmeter.apache.org
>>> >
>>>
>>>
>>>
>>> --
>>>
>>>
>>> Regulatory, Medical & Performance Testing Services:
>>>
>>>
>>> * IEC 62304 Medical Device Software Life Cycle
>>>
>>> * IEEE 829 Software Test Documentation
>>>
>>> * ISO 14971 Medical Device Risk Management
>>>
>>> * FDA 21 CFR Part 11 Software Validation
>>>
>>> * IEC 60601-1:2005 3rd ED PEMS - Medical Electrical Equipment
>>>
>>> * End-to-end verification, validation, and testing (VV&T)
>>>
>>> * High quality service for FDA and CE submissions
>>>
>>> * Reliable open source free testing tools
>>>
>>> * Optional functionality and regression testing
>>>
>>> * Software Performance & Load Testing
>>>
>>> * Software Testing Advanced Automation
>>>
>>> * Medical Software Verification & Validation
>>>
>>> * Medical Device Verification & Validation
>>>
>>> * Medical Device Regulatory Submission
>>>
>>> * Organizational Regulatory Qualification
>>>
>>>
>>>
>>> Shay Ginsbourg
>>>
>>> Regulatory & Testing Affairs Consultant
>>>
>>>
>>>
>>> Formerly QA Manager of LoadRunner at Mercury Interactive
>>>
>>>
>>> M.Sc. cum laude in Bio-Medical Engineering
>>>
>>> M.Sc. in Mechanical Engineering
>>>
>>>
>>>
>>>
>>> Work: 035185873
>>>
>>> Mobile: 0546690915
>>>
>>>
>>> Email: sginsbourg@gmail.com
>>>
>>>
>>> http://il.linkedin.com/in/shayginsbourg
>>>
>>>
>>> WWW.GINSBOURG.COM
>>>
>>>
>>>
>>>
>>>
>>> Please consider your environmental responsibility before printing this
>>> e-mail.
>>>
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
For additional commands, e-mail: user-help@jmeter.apache.org
Re: Website Login Issue
Posted by Ryan <gr...@gmail.com>.
Does anyone have any ideas on this? We're still having this issue. I've
made sure that the VIEWSTATE is captured, et cetera. Everything seems to be
in order but something still isn't happy. This is a really simple test
case, so I'm confused as to why it isn't working.
On Wed, Mar 7, 2012 at 5:12 PM, Ryan <gr...@gmail.com> wrote:
> The application doesn't use OAuth, so that does not apply here. Surely
> someone out there has an idea on how to get this to work?
>
>
> On Wed, Mar 7, 2012 at 3:43 PM, Shay Ginsbourg <sg...@gmail.com>wrote:
>
>> 1. Should check the possibility of working with -> "JMeter OAuth Sampler".
>>
>> 2. Also, can download 30-days trial free RADVIEW WEBLOAD -> record,
>> replay,
>> auto-correlate, and gain some new insight into your Jmeter script.
>>
>> Good luck!
>> Shay
>>
>>
>>
>> On Wed, Mar 7, 2012 at 22:15, Ryan <gr...@gmail.com> wrote:
>>
>> > I've double checked everything that the browser requests and all
>> > parameters match up with the JMeter http request configuration for the
>> > login action, including the ASP.Net parameters. I'm using JMeter 2.6,
>> for
>> > the record.
>> >
>> > I've attached an image showing the request configuration, the actual
>> > request contents and the browser's request contents for comparison.
>> >
>> > On Mon, Mar 5, 2012 at 3:09 PM, Deepak Shetty <sh...@gmail.com>
>> wrote:
>> >
>> >> your probably not extracting out the dynamic asp.net parameters
>> >> (viewstate
>> >> ,eventvalidation etc)
>> >> otherwise compare what browser sends and receives.
>> >>
>> >> regards
>> >> deepak
>> >>
>> >> On Mon, Mar 5, 2012 at 12:57 PM, Ryan <gr...@gmail.com> wrote:
>> >>
>> >> > It's been a while since I've used JMeter and recently started using
>> it
>> >> > again to test one of our webapps here. It is a pretty standard
>> ASP.Net 4
>> >> > app, nothing crazy. I implemented a simple test script just to make
>> sure
>> >> > login works as expected, but I cannot get this thing to work.
>> >> >
>> >> > The steps are pretty simple:
>> >> > /login.aspx
>> >> > /default.aspx
>> >> > /logout.aspx
>> >> > /login.aspx
>> >> >
>> >> > For the first login.aspx call, I'm including two parameters in the
>> POST
>> >> to
>> >> > pass the login name and password values that are expected. In my View
>> >> > Results Tree, this step does include the correct POST data and login
>> >> > parameters.
>> >> >
>> >> > However, once it moves to the /default.aspx step, the only response I
>> >> get
>> >> > is:
>> >> >
>> >> > <html><head><title>Object moved</title></head><body>
>> >> > <h2>Object moved to <a href="/timeout.aspx">here</a>.</h2>
>> >> > </body></html>
>> >> >
>> >> > It then adds a step calling the /timeout.aspx page, which outputs the
>> >> > following response:
>> >> >
>> >> > <html><head><title>Object moved</title></head><body>
>> >> > <h2>Object moved to <a href="/login.aspx">here</a>.</h2>
>> >> > </body></html>
>> >> >
>> >> > It then calls the /login.aspx page. This is the correct behavior if
>> the
>> >> > user is not logged in any longer (meaning a specific session value
>> is no
>> >> > longer valid or has been removed)...it redirects to /timeout.aspx
>> which
>> >> > then forwards to /login.aspx. The question is why this is happening,
>> as
>> >> > this is not what happens in the browser.
>> >> >
>> >> > I have an HTTP Cookie Manager to store the session values, and the
>> >> session
>> >> > cookie is showing up in the step request.
>> >> >
>> >> > I figured I screwed something up so I recorded a test script with the
>> >> HTTP
>> >> > Proxy Server and it gave me the exact same steps and results as when
>> I
>> >> > manually created it, so I'm stuck at this point. I've double-checked
>> the
>> >> > web site script tutorials on the JMeter site as well as around the
>> web
>> >> and
>> >> > it should be working.
>> >> >
>> >> > Any ideas? Any help would be appreciated.
>> >> >
>> >>
>> >
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
>> > For additional commands, e-mail: user-help@jmeter.apache.org
>> >
>>
>>
>>
>> --
>>
>>
>> Regulatory, Medical & Performance Testing Services:
>>
>>
>> * IEC 62304 Medical Device Software Life Cycle
>>
>> * IEEE 829 Software Test Documentation
>>
>> * ISO 14971 Medical Device Risk Management
>>
>> * FDA 21 CFR Part 11 Software Validation
>>
>> * IEC 60601-1:2005 3rd ED PEMS - Medical Electrical Equipment
>>
>> * End-to-end verification, validation, and testing (VV&T)
>>
>> * High quality service for FDA and CE submissions
>>
>> * Reliable open source free testing tools
>>
>> * Optional functionality and regression testing
>>
>> * Software Performance & Load Testing
>>
>> * Software Testing Advanced Automation
>>
>> * Medical Software Verification & Validation
>>
>> * Medical Device Verification & Validation
>>
>> * Medical Device Regulatory Submission
>>
>> * Organizational Regulatory Qualification
>>
>>
>>
>> Shay Ginsbourg
>>
>> Regulatory & Testing Affairs Consultant
>>
>>
>>
>> Formerly QA Manager of LoadRunner at Mercury Interactive
>>
>>
>> M.Sc. cum laude in Bio-Medical Engineering
>>
>> M.Sc. in Mechanical Engineering
>>
>>
>>
>>
>> Work: 035185873
>>
>> Mobile: 0546690915
>>
>>
>> Email: sginsbourg@gmail.com
>>
>>
>> http://il.linkedin.com/in/shayginsbourg
>>
>>
>> WWW.GINSBOURG.COM
>>
>>
>>
>>
>>
>> Please consider your environmental responsibility before printing this
>> e-mail.
>>
>
>
Re: Website Login Issue
Posted by Ryan <gr...@gmail.com>.
The application doesn't use OAuth, so that does not apply here. Surely
someone out there has an idea on how to get this to work?
On Wed, Mar 7, 2012 at 3:43 PM, Shay Ginsbourg <sg...@gmail.com> wrote:
> 1. Should check the possibility of working with -> "JMeter OAuth Sampler".
>
> 2. Also, can download 30-days trial free RADVIEW WEBLOAD -> record, replay,
> auto-correlate, and gain some new insight into your Jmeter script.
>
> Good luck!
> Shay
>
>
>
> On Wed, Mar 7, 2012 at 22:15, Ryan <gr...@gmail.com> wrote:
>
> > I've double checked everything that the browser requests and all
> > parameters match up with the JMeter http request configuration for the
> > login action, including the ASP.Net parameters. I'm using JMeter 2.6, for
> > the record.
> >
> > I've attached an image showing the request configuration, the actual
> > request contents and the browser's request contents for comparison.
> >
> > On Mon, Mar 5, 2012 at 3:09 PM, Deepak Shetty <sh...@gmail.com> wrote:
> >
> >> your probably not extracting out the dynamic asp.net parameters
> >> (viewstate
> >> ,eventvalidation etc)
> >> otherwise compare what browser sends and receives.
> >>
> >> regards
> >> deepak
> >>
> >> On Mon, Mar 5, 2012 at 12:57 PM, Ryan <gr...@gmail.com> wrote:
> >>
> >> > It's been a while since I've used JMeter and recently started using it
> >> > again to test one of our webapps here. It is a pretty standard
> ASP.Net 4
> >> > app, nothing crazy. I implemented a simple test script just to make
> sure
> >> > login works as expected, but I cannot get this thing to work.
> >> >
> >> > The steps are pretty simple:
> >> > /login.aspx
> >> > /default.aspx
> >> > /logout.aspx
> >> > /login.aspx
> >> >
> >> > For the first login.aspx call, I'm including two parameters in the
> POST
> >> to
> >> > pass the login name and password values that are expected. In my View
> >> > Results Tree, this step does include the correct POST data and login
> >> > parameters.
> >> >
> >> > However, once it moves to the /default.aspx step, the only response I
> >> get
> >> > is:
> >> >
> >> > <html><head><title>Object moved</title></head><body>
> >> > <h2>Object moved to <a href="/timeout.aspx">here</a>.</h2>
> >> > </body></html>
> >> >
> >> > It then adds a step calling the /timeout.aspx page, which outputs the
> >> > following response:
> >> >
> >> > <html><head><title>Object moved</title></head><body>
> >> > <h2>Object moved to <a href="/login.aspx">here</a>.</h2>
> >> > </body></html>
> >> >
> >> > It then calls the /login.aspx page. This is the correct behavior if
> the
> >> > user is not logged in any longer (meaning a specific session value is
> no
> >> > longer valid or has been removed)...it redirects to /timeout.aspx
> which
> >> > then forwards to /login.aspx. The question is why this is happening,
> as
> >> > this is not what happens in the browser.
> >> >
> >> > I have an HTTP Cookie Manager to store the session values, and the
> >> session
> >> > cookie is showing up in the step request.
> >> >
> >> > I figured I screwed something up so I recorded a test script with the
> >> HTTP
> >> > Proxy Server and it gave me the exact same steps and results as when I
> >> > manually created it, so I'm stuck at this point. I've double-checked
> the
> >> > web site script tutorials on the JMeter site as well as around the web
> >> and
> >> > it should be working.
> >> >
> >> > Any ideas? Any help would be appreciated.
> >> >
> >>
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> > For additional commands, e-mail: user-help@jmeter.apache.org
> >
>
>
>
> --
>
>
> Regulatory, Medical & Performance Testing Services:
>
>
> * IEC 62304 Medical Device Software Life Cycle
>
> * IEEE 829 Software Test Documentation
>
> * ISO 14971 Medical Device Risk Management
>
> * FDA 21 CFR Part 11 Software Validation
>
> * IEC 60601-1:2005 3rd ED PEMS - Medical Electrical Equipment
>
> * End-to-end verification, validation, and testing (VV&T)
>
> * High quality service for FDA and CE submissions
>
> * Reliable open source free testing tools
>
> * Optional functionality and regression testing
>
> * Software Performance & Load Testing
>
> * Software Testing Advanced Automation
>
> * Medical Software Verification & Validation
>
> * Medical Device Verification & Validation
>
> * Medical Device Regulatory Submission
>
> * Organizational Regulatory Qualification
>
>
>
> Shay Ginsbourg
>
> Regulatory & Testing Affairs Consultant
>
>
>
> Formerly QA Manager of LoadRunner at Mercury Interactive
>
>
> M.Sc. cum laude in Bio-Medical Engineering
>
> M.Sc. in Mechanical Engineering
>
>
>
>
> Work: 035185873
>
> Mobile: 0546690915
>
>
> Email: sginsbourg@gmail.com
>
>
> http://il.linkedin.com/in/shayginsbourg
>
>
> WWW.GINSBOURG.COM
>
>
>
>
>
> Please consider your environmental responsibility before printing this
> e-mail.
>
Re: Website Login Issue
Posted by Shay Ginsbourg <sg...@gmail.com>.
1. Should check the possibility of working with -> "JMeter OAuth Sampler".
2. Also, can download 30-days trial free RADVIEW WEBLOAD -> record, replay,
auto-correlate, and gain some new insight into your Jmeter script.
Good luck!
Shay
On Wed, Mar 7, 2012 at 22:15, Ryan <gr...@gmail.com> wrote:
> I've double checked everything that the browser requests and all
> parameters match up with the JMeter http request configuration for the
> login action, including the ASP.Net parameters. I'm using JMeter 2.6, for
> the record.
>
> I've attached an image showing the request configuration, the actual
> request contents and the browser's request contents for comparison.
>
> On Mon, Mar 5, 2012 at 3:09 PM, Deepak Shetty <sh...@gmail.com> wrote:
>
>> your probably not extracting out the dynamic asp.net parameters
>> (viewstate
>> ,eventvalidation etc)
>> otherwise compare what browser sends and receives.
>>
>> regards
>> deepak
>>
>> On Mon, Mar 5, 2012 at 12:57 PM, Ryan <gr...@gmail.com> wrote:
>>
>> > It's been a while since I've used JMeter and recently started using it
>> > again to test one of our webapps here. It is a pretty standard ASP.Net 4
>> > app, nothing crazy. I implemented a simple test script just to make sure
>> > login works as expected, but I cannot get this thing to work.
>> >
>> > The steps are pretty simple:
>> > /login.aspx
>> > /default.aspx
>> > /logout.aspx
>> > /login.aspx
>> >
>> > For the first login.aspx call, I'm including two parameters in the POST
>> to
>> > pass the login name and password values that are expected. In my View
>> > Results Tree, this step does include the correct POST data and login
>> > parameters.
>> >
>> > However, once it moves to the /default.aspx step, the only response I
>> get
>> > is:
>> >
>> > <html><head><title>Object moved</title></head><body>
>> > <h2>Object moved to <a href="/timeout.aspx">here</a>.</h2>
>> > </body></html>
>> >
>> > It then adds a step calling the /timeout.aspx page, which outputs the
>> > following response:
>> >
>> > <html><head><title>Object moved</title></head><body>
>> > <h2>Object moved to <a href="/login.aspx">here</a>.</h2>
>> > </body></html>
>> >
>> > It then calls the /login.aspx page. This is the correct behavior if the
>> > user is not logged in any longer (meaning a specific session value is no
>> > longer valid or has been removed)...it redirects to /timeout.aspx which
>> > then forwards to /login.aspx. The question is why this is happening, as
>> > this is not what happens in the browser.
>> >
>> > I have an HTTP Cookie Manager to store the session values, and the
>> session
>> > cookie is showing up in the step request.
>> >
>> > I figured I screwed something up so I recorded a test script with the
>> HTTP
>> > Proxy Server and it gave me the exact same steps and results as when I
>> > manually created it, so I'm stuck at this point. I've double-checked the
>> > web site script tutorials on the JMeter site as well as around the web
>> and
>> > it should be working.
>> >
>> > Any ideas? Any help would be appreciated.
>> >
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> For additional commands, e-mail: user-help@jmeter.apache.org
>
--
Regulatory, Medical & Performance Testing Services:
* IEC 62304 Medical Device Software Life Cycle
* IEEE 829 Software Test Documentation
* ISO 14971 Medical Device Risk Management
* FDA 21 CFR Part 11 Software Validation
* IEC 60601-1:2005 3rd ED PEMS - Medical Electrical Equipment
* End-to-end verification, validation, and testing (VV&T)
* High quality service for FDA and CE submissions
* Reliable open source free testing tools
* Optional functionality and regression testing
* Software Performance & Load Testing
* Software Testing Advanced Automation
* Medical Software Verification & Validation
* Medical Device Verification & Validation
* Medical Device Regulatory Submission
* Organizational Regulatory Qualification
Shay Ginsbourg
Regulatory & Testing Affairs Consultant
Formerly QA Manager of LoadRunner at Mercury Interactive
M.Sc. cum laude in Bio-Medical Engineering
M.Sc. in Mechanical Engineering
Work: 035185873
Mobile: 0546690915
Email: sginsbourg@gmail.com
http://il.linkedin.com/in/shayginsbourg
WWW.GINSBOURG.COM
Please consider your environmental responsibility before printing this
e-mail.
Re: Website Login Issue
Posted by Ryan <gr...@gmail.com>.
I've double checked everything that the browser requests and all parameters
match up with the JMeter http request configuration for the login action,
including the ASP.Net parameters. I'm using JMeter 2.6, for the record.
I've attached an image showing the request configuration, the actual
request contents and the browser's request contents for comparison.
On Mon, Mar 5, 2012 at 3:09 PM, Deepak Shetty <sh...@gmail.com> wrote:
> your probably not extracting out the dynamic asp.net parameters (viewstate
> ,eventvalidation etc)
> otherwise compare what browser sends and receives.
>
> regards
> deepak
>
> On Mon, Mar 5, 2012 at 12:57 PM, Ryan <gr...@gmail.com> wrote:
>
> > It's been a while since I've used JMeter and recently started using it
> > again to test one of our webapps here. It is a pretty standard ASP.Net 4
> > app, nothing crazy. I implemented a simple test script just to make sure
> > login works as expected, but I cannot get this thing to work.
> >
> > The steps are pretty simple:
> > /login.aspx
> > /default.aspx
> > /logout.aspx
> > /login.aspx
> >
> > For the first login.aspx call, I'm including two parameters in the POST
> to
> > pass the login name and password values that are expected. In my View
> > Results Tree, this step does include the correct POST data and login
> > parameters.
> >
> > However, once it moves to the /default.aspx step, the only response I get
> > is:
> >
> > <html><head><title>Object moved</title></head><body>
> > <h2>Object moved to <a href="/timeout.aspx">here</a>.</h2>
> > </body></html>
> >
> > It then adds a step calling the /timeout.aspx page, which outputs the
> > following response:
> >
> > <html><head><title>Object moved</title></head><body>
> > <h2>Object moved to <a href="/login.aspx">here</a>.</h2>
> > </body></html>
> >
> > It then calls the /login.aspx page. This is the correct behavior if the
> > user is not logged in any longer (meaning a specific session value is no
> > longer valid or has been removed)...it redirects to /timeout.aspx which
> > then forwards to /login.aspx. The question is why this is happening, as
> > this is not what happens in the browser.
> >
> > I have an HTTP Cookie Manager to store the session values, and the
> session
> > cookie is showing up in the step request.
> >
> > I figured I screwed something up so I recorded a test script with the
> HTTP
> > Proxy Server and it gave me the exact same steps and results as when I
> > manually created it, so I'm stuck at this point. I've double-checked the
> > web site script tutorials on the JMeter site as well as around the web
> and
> > it should be working.
> >
> > Any ideas? Any help would be appreciated.
> >
>
Re: Website Login Issue
Posted by Deepak Shetty <sh...@gmail.com>.
your probably not extracting out the dynamic asp.net parameters (viewstate
,eventvalidation etc)
otherwise compare what browser sends and receives.
regards
deepak
On Mon, Mar 5, 2012 at 12:57 PM, Ryan <gr...@gmail.com> wrote:
> It's been a while since I've used JMeter and recently started using it
> again to test one of our webapps here. It is a pretty standard ASP.Net 4
> app, nothing crazy. I implemented a simple test script just to make sure
> login works as expected, but I cannot get this thing to work.
>
> The steps are pretty simple:
> /login.aspx
> /default.aspx
> /logout.aspx
> /login.aspx
>
> For the first login.aspx call, I'm including two parameters in the POST to
> pass the login name and password values that are expected. In my View
> Results Tree, this step does include the correct POST data and login
> parameters.
>
> However, once it moves to the /default.aspx step, the only response I get
> is:
>
> <html><head><title>Object moved</title></head><body>
> <h2>Object moved to <a href="/timeout.aspx">here</a>.</h2>
> </body></html>
>
> It then adds a step calling the /timeout.aspx page, which outputs the
> following response:
>
> <html><head><title>Object moved</title></head><body>
> <h2>Object moved to <a href="/login.aspx">here</a>.</h2>
> </body></html>
>
> It then calls the /login.aspx page. This is the correct behavior if the
> user is not logged in any longer (meaning a specific session value is no
> longer valid or has been removed)...it redirects to /timeout.aspx which
> then forwards to /login.aspx. The question is why this is happening, as
> this is not what happens in the browser.
>
> I have an HTTP Cookie Manager to store the session values, and the session
> cookie is showing up in the step request.
>
> I figured I screwed something up so I recorded a test script with the HTTP
> Proxy Server and it gave me the exact same steps and results as when I
> manually created it, so I'm stuck at this point. I've double-checked the
> web site script tutorials on the JMeter site as well as around the web and
> it should be working.
>
> Any ideas? Any help would be appreciated.
>