You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by Arijit Mukherjee <ar...@gmail.com> on 2010/01/07 10:41:48 UTC
Problem with HTTPS login
Hi All
I'm struggling with a JMeter/HTTPS issue for the past couple of days
and am just short of banging my head against the desk. I searched the
net and found a JMeter patch
(https://issues.apache.org/bugzilla/show_bug.cgi?id=47622) which is
able to record HTTPS requests using the JMeter Proxy Server - and
people have been able to log onto gmail etc. using this patch
(http://www.mail-archive.com/jmeter-dev@jakarta.apache.org/msg19865.html)
I've downloaded this patch (and the latest nightly build as well -
r894536), and have been trying to replay the script to log on to
gmail. But all I see as the response from the server is the login
screen of gmail. I browsed the mail archive and tried adding an
Authorization Manager, HTTP Cookie Manager to the thread group, but
the ultimate result is the same - on the results tree, most of the
steps (green button - apparently success) show the gmail login screen,
and some of the steps (red marks) return "unauthorized".
It seems like some session related issue which I'm not able to track
down. Can someone please help me?
Regards
Arijit
--
"And when the night is cloudy,
There is still a light that shines on me,
Shine on until tomorrow, let it be."
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: Problem with HTTPS login
Posted by sebb <se...@gmail.com>.
On 08/01/2010, Rod MacPherson <rm...@healthation.com> wrote:
> This is going to be increasingly problematic as rich internet
> applications become the standard. JMeter does not run JavaScript so if
> your page is initializing data that is subsequently required as part of
> the form post or query string, it will fail.
>
> Functional test products like BadBoy do not run the JavaScript on a
> page, either. As a workaround, they let you add JavaScript elements to
> your test steps that get run during testing.
JMeter has programmable Processors (BeanShell and BSF) which are similar.
> JMeter could be enhanced to embed Rhino (de facto standard JavaScript
> engine), capture script and execute it. Sounds like a big job to get
> that right. It's unfortunate that JMeter was not designed from the
> outset as an API that you could bolt your own GUI on. That would have
> provided an excellent platform for all kinds of tooling.
JMeter *was* designed for extension - you can easily add your own
samplers and other test elements. Most of the existing JMeter elements
are add-ons in the sense that they can be removed and the core JMeter
will still work. For example, you can remove ApacheJMeter_jdbc.jar and
there will be no JDBC samplers, but the rest of JMeter will work.
> Another alternative is Web Testing in Ruby or .NET or Java which I have
> dubbed WATIX APIs (they have WATIR, WATIN...) but they do not scale well
> (Browser Mob solves that using with unlimited servers in the Amazon
> cloud -- limited by cash on hand:) Then again, they have to corral all
> of the info from all those servers, like JMeter does.
>
>
> -----Original Message-----
> From: Arijit Mukherjee [mailto:arijit72@gmail.com]
> Sent: Thursday, January 07, 2010 8:41 PM
> To: JMeter Users List
> Subject: Re: Problem with HTTPS login
>
> Hi Deepak
>
> The local setup we want to test is giving similar problems - only the
> login screen when the recorded script is used. I was wondering if I
> could get a sample for gmail - to find out what exactly I should do.
> It seemed from the bugzilla page (the one I referred to earlier) that
> the script recorded by the proxy is sufficient...
>
> Regards
> Arijit
>
> 2010/1/7 Deepak Shetty <sh...@gmail.com>:
> > Hi
> > Gmail uses a lot of dynamically generated variables, unless you sit
> and
> > identify each one of these and replace them to be extracted via post
> > processors, you will get errors.
> > If GMail is just a test then I suggest you dont use that for writing
> sample
> > scripts and use an environment closer to yours.
> >
> >
> > regards
> > deepak
> >
> > On Thu, Jan 7, 2010 at 5:07 AM, Arijit Mukherjee <ar...@gmail.com>
> wrote:
> >
> >> A follow-up:
> >>
> >> I've been able to record the steps to login to another website
> >> (www.epw.in) and replay back the script successfully. But it's still
> a
> >> no go for gmail. Here's what I have right now:
> >>
> >> (1) In jmeter.properties: CookieManager.save.cookies=true
> >> (2) Added a proxy server to the workbench
> >> (3) Added a thread-group, and a HTTP Cookie Manager to the thread
> group
> >> (4) Proxy Target recording: Test Plant -> Thread Group, rest of the
> >> options default, started the proxy
> >> (5) Directed the browser to use JMeter proxy (for all protocols), and
> >> logged into gmail - script was recorded
> >> (6) replayed the script - and got back the login page for almost all
> >> steps, and some "401" errors
> >>
> >> It seems if you create the script manually you can add a "URL
> >> rewriting" element to each of the steps which might work. But for me
> >> this gmail login is just a test - I am trying to create scripts for
> >> load testing our server which would involve too many steps to edit
> >> them manually. We've also tried rerunning a badboy generated script
> >> and the same thing happens for gmail.
> >>
> >> Hoping that someone will be able to throw some light...
> >>
> >> Arijit
> >>
> >> 2010/1/7 Arijit Mukherjee <ar...@gmail.com>:
> >> > Hi All
> >> >
> >> > I'm struggling with a JMeter/HTTPS issue for the past couple of
> days
> >> > and am just short of banging my head against the desk. I searched
> the
> >> > net and found a JMeter patch
> >> > (https://issues.apache.org/bugzilla/show_bug.cgi?id=47622) which is
> >> > able to record HTTPS requests using the JMeter Proxy Server - and
> >> > people have been able to log onto gmail etc. using this patch
> >> >
> (http://www.mail-archive.com/jmeter-dev@jakarta.apache.org/msg19865.html
> >> )
> >> >
> >> > I've downloaded this patch (and the latest nightly build as well -
> >> > r894536), and have been trying to replay the script to log on to
> >> > gmail. But all I see as the response from the server is the login
> >> > screen of gmail. I browsed the mail archive and tried adding an
> >> > Authorization Manager, HTTP Cookie Manager to the thread group, but
> >> > the ultimate result is the same - on the results tree, most of the
> >> > steps (green button - apparently success) show the gmail login
> screen,
> >> > and some of the steps (red marks) return "unauthorized".
> >> >
> >> > It seems like some session related issue which I'm not able to
> track
> >> > down. Can someone please help me?
> >> >
> >> > Regards
> >> > Arijit
> >> >
> >> > --
> >> > "And when the night is cloudy,
> >> > There is still a light that shines on me,
> >> > Shine on until tomorrow, let it be."
> >> >
> >>
> >>
> >>
> >> --
> >> "And when the night is cloudy,
> >> There is still a light that shines on me,
> >> Shine on until tomorrow, let it be."
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> >> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> >>
> >>
> >
>
>
>
> --
> "And when the night is cloudy,
> There is still a light that shines on me,
> Shine on until tomorrow, let it be."
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
RE: Problem with HTTPS login
Posted by Rod MacPherson <rm...@healthation.com>.
This is going to be increasingly problematic as rich internet
applications become the standard. JMeter does not run JavaScript so if
your page is initializing data that is subsequently required as part of
the form post or query string, it will fail.
Functional test products like BadBoy do not run the JavaScript on a
page, either. As a workaround, they let you add JavaScript elements to
your test steps that get run during testing.
JMeter could be enhanced to embed Rhino (de facto standard JavaScript
engine), capture script and execute it. Sounds like a big job to get
that right. It's unfortunate that JMeter was not designed from the
outset as an API that you could bolt your own GUI on. That would have
provided an excellent platform for all kinds of tooling.
Another alternative is Web Testing in Ruby or .NET or Java which I have
dubbed WATIX APIs (they have WATIR, WATIN...) but they do not scale well
(Browser Mob solves that using with unlimited servers in the Amazon
cloud -- limited by cash on hand:) Then again, they have to corral all
of the info from all those servers, like JMeter does.
-----Original Message-----
From: Arijit Mukherjee [mailto:arijit72@gmail.com]
Sent: Thursday, January 07, 2010 8:41 PM
To: JMeter Users List
Subject: Re: Problem with HTTPS login
Hi Deepak
The local setup we want to test is giving similar problems - only the
login screen when the recorded script is used. I was wondering if I
could get a sample for gmail - to find out what exactly I should do.
It seemed from the bugzilla page (the one I referred to earlier) that
the script recorded by the proxy is sufficient...
Regards
Arijit
2010/1/7 Deepak Shetty <sh...@gmail.com>:
> Hi
> Gmail uses a lot of dynamically generated variables, unless you sit
and
> identify each one of these and replace them to be extracted via post
> processors, you will get errors.
> If GMail is just a test then I suggest you dont use that for writing
sample
> scripts and use an environment closer to yours.
>
>
> regards
> deepak
>
> On Thu, Jan 7, 2010 at 5:07 AM, Arijit Mukherjee <ar...@gmail.com>
wrote:
>
>> A follow-up:
>>
>> I've been able to record the steps to login to another website
>> (www.epw.in) and replay back the script successfully. But it's still
a
>> no go for gmail. Here's what I have right now:
>>
>> (1) In jmeter.properties: CookieManager.save.cookies=true
>> (2) Added a proxy server to the workbench
>> (3) Added a thread-group, and a HTTP Cookie Manager to the thread
group
>> (4) Proxy Target recording: Test Plant -> Thread Group, rest of the
>> options default, started the proxy
>> (5) Directed the browser to use JMeter proxy (for all protocols), and
>> logged into gmail - script was recorded
>> (6) replayed the script - and got back the login page for almost all
>> steps, and some "401" errors
>>
>> It seems if you create the script manually you can add a "URL
>> rewriting" element to each of the steps which might work. But for me
>> this gmail login is just a test - I am trying to create scripts for
>> load testing our server which would involve too many steps to edit
>> them manually. We've also tried rerunning a badboy generated script
>> and the same thing happens for gmail.
>>
>> Hoping that someone will be able to throw some light...
>>
>> Arijit
>>
>> 2010/1/7 Arijit Mukherjee <ar...@gmail.com>:
>> > Hi All
>> >
>> > I'm struggling with a JMeter/HTTPS issue for the past couple of
days
>> > and am just short of banging my head against the desk. I searched
the
>> > net and found a JMeter patch
>> > (https://issues.apache.org/bugzilla/show_bug.cgi?id=47622) which is
>> > able to record HTTPS requests using the JMeter Proxy Server - and
>> > people have been able to log onto gmail etc. using this patch
>> >
(http://www.mail-archive.com/jmeter-dev@jakarta.apache.org/msg19865.html
>> )
>> >
>> > I've downloaded this patch (and the latest nightly build as well -
>> > r894536), and have been trying to replay the script to log on to
>> > gmail. But all I see as the response from the server is the login
>> > screen of gmail. I browsed the mail archive and tried adding an
>> > Authorization Manager, HTTP Cookie Manager to the thread group, but
>> > the ultimate result is the same - on the results tree, most of the
>> > steps (green button - apparently success) show the gmail login
screen,
>> > and some of the steps (red marks) return "unauthorized".
>> >
>> > It seems like some session related issue which I'm not able to
track
>> > down. Can someone please help me?
>> >
>> > Regards
>> > Arijit
>> >
>> > --
>> > "And when the night is cloudy,
>> > There is still a light that shines on me,
>> > Shine on until tomorrow, let it be."
>> >
>>
>>
>>
>> --
>> "And when the night is cloudy,
>> There is still a light that shines on me,
>> Shine on until tomorrow, let it be."
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>>
>>
>
--
"And when the night is cloudy,
There is still a light that shines on me,
Shine on until tomorrow, let it be."
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: Problem with HTTPS login
Posted by Deepak Shetty <sh...@gmail.com>.
Hi
Easier to diagnose your system since you know the code (or know someone who
does) than gmail. A recorded script is not guaranteed to work.
You need to record what your browser does (using LiveHTTPHeaders/Fiddler). I
assume the site works through a browser :).
And contrast with what your test does using View results Tree Listener in
JMeter (also use render as html to see that the response looks correct and
no errors were received e.g. your account is locked! - you should have
response assertions).
You need to check every step and see whether any data is dynamic, whether
the protocols all match , whether similar cookies are sent. You also
probably should check Follow Redirects instead of Redirect Automatically on
your samplers
and finally
http://wiki.apache.org/jakarta-jmeter/DifferentBehaviour.
If you still have problems you might upload the browser trace and your
Jmeter View Results Tree requests/response and post links to them here
regards
deepak
On Thu, Jan 7, 2010 at 8:40 PM, Arijit Mukherjee <ar...@gmail.com> wrote:
> Hi Deepak
>
> The local setup we want to test is giving similar problems - only the
> login screen when the recorded script is used. I was wondering if I
> could get a sample for gmail - to find out what exactly I should do.
> It seemed from the bugzilla page (the one I referred to earlier) that
> the script recorded by the proxy is sufficient...
>
> Regards
> Arijit
>
> 2010/1/7 Deepak Shetty <sh...@gmail.com>:
> > Hi
> > Gmail uses a lot of dynamically generated variables, unless you sit and
> > identify each one of these and replace them to be extracted via post
> > processors, you will get errors.
> > If GMail is just a test then I suggest you dont use that for writing
> sample
> > scripts and use an environment closer to yours.
> >
> >
> > regards
> > deepak
> >
> > On Thu, Jan 7, 2010 at 5:07 AM, Arijit Mukherjee <ar...@gmail.com>
> wrote:
> >
> >> A follow-up:
> >>
> >> I've been able to record the steps to login to another website
> >> (www.epw.in) and replay back the script successfully. But it's still a
> >> no go for gmail. Here's what I have right now:
> >>
> >> (1) In jmeter.properties: CookieManager.save.cookies=true
> >> (2) Added a proxy server to the workbench
> >> (3) Added a thread-group, and a HTTP Cookie Manager to the thread group
> >> (4) Proxy Target recording: Test Plant -> Thread Group, rest of the
> >> options default, started the proxy
> >> (5) Directed the browser to use JMeter proxy (for all protocols), and
> >> logged into gmail - script was recorded
> >> (6) replayed the script - and got back the login page for almost all
> >> steps, and some "401" errors
> >>
> >> It seems if you create the script manually you can add a "URL
> >> rewriting" element to each of the steps which might work. But for me
> >> this gmail login is just a test - I am trying to create scripts for
> >> load testing our server which would involve too many steps to edit
> >> them manually. We've also tried rerunning a badboy generated script
> >> and the same thing happens for gmail.
> >>
> >> Hoping that someone will be able to throw some light...
> >>
> >> Arijit
> >>
> >> 2010/1/7 Arijit Mukherjee <ar...@gmail.com>:
> >> > Hi All
> >> >
> >> > I'm struggling with a JMeter/HTTPS issue for the past couple of days
> >> > and am just short of banging my head against the desk. I searched the
> >> > net and found a JMeter patch
> >> > (https://issues.apache.org/bugzilla/show_bug.cgi?id=47622) which is
> >> > able to record HTTPS requests using the JMeter Proxy Server - and
> >> > people have been able to log onto gmail etc. using this patch
> >> > (
> http://www.mail-archive.com/jmeter-dev@jakarta.apache.org/msg19865.html
> >> )
> >> >
> >> > I've downloaded this patch (and the latest nightly build as well -
> >> > r894536), and have been trying to replay the script to log on to
> >> > gmail. But all I see as the response from the server is the login
> >> > screen of gmail. I browsed the mail archive and tried adding an
> >> > Authorization Manager, HTTP Cookie Manager to the thread group, but
> >> > the ultimate result is the same - on the results tree, most of the
> >> > steps (green button - apparently success) show the gmail login screen,
> >> > and some of the steps (red marks) return "unauthorized".
> >> >
> >> > It seems like some session related issue which I'm not able to track
> >> > down. Can someone please help me?
> >> >
> >> > Regards
> >> > Arijit
> >> >
> >> > --
> >> > "And when the night is cloudy,
> >> > There is still a light that shines on me,
> >> > Shine on until tomorrow, let it be."
> >> >
> >>
> >>
> >>
> >> --
> >> "And when the night is cloudy,
> >> There is still a light that shines on me,
> >> Shine on until tomorrow, let it be."
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> >> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> >>
> >>
> >
>
>
>
> --
> "And when the night is cloudy,
> There is still a light that shines on me,
> Shine on until tomorrow, let it be."
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
Re: Problem with HTTPS login
Posted by Arijit Mukherjee <ar...@gmail.com>.
Hi Deepak
The local setup we want to test is giving similar problems - only the
login screen when the recorded script is used. I was wondering if I
could get a sample for gmail - to find out what exactly I should do.
It seemed from the bugzilla page (the one I referred to earlier) that
the script recorded by the proxy is sufficient...
Regards
Arijit
2010/1/7 Deepak Shetty <sh...@gmail.com>:
> Hi
> Gmail uses a lot of dynamically generated variables, unless you sit and
> identify each one of these and replace them to be extracted via post
> processors, you will get errors.
> If GMail is just a test then I suggest you dont use that for writing sample
> scripts and use an environment closer to yours.
>
>
> regards
> deepak
>
> On Thu, Jan 7, 2010 at 5:07 AM, Arijit Mukherjee <ar...@gmail.com> wrote:
>
>> A follow-up:
>>
>> I've been able to record the steps to login to another website
>> (www.epw.in) and replay back the script successfully. But it's still a
>> no go for gmail. Here's what I have right now:
>>
>> (1) In jmeter.properties: CookieManager.save.cookies=true
>> (2) Added a proxy server to the workbench
>> (3) Added a thread-group, and a HTTP Cookie Manager to the thread group
>> (4) Proxy Target recording: Test Plant -> Thread Group, rest of the
>> options default, started the proxy
>> (5) Directed the browser to use JMeter proxy (for all protocols), and
>> logged into gmail - script was recorded
>> (6) replayed the script - and got back the login page for almost all
>> steps, and some "401" errors
>>
>> It seems if you create the script manually you can add a "URL
>> rewriting" element to each of the steps which might work. But for me
>> this gmail login is just a test - I am trying to create scripts for
>> load testing our server which would involve too many steps to edit
>> them manually. We've also tried rerunning a badboy generated script
>> and the same thing happens for gmail.
>>
>> Hoping that someone will be able to throw some light...
>>
>> Arijit
>>
>> 2010/1/7 Arijit Mukherjee <ar...@gmail.com>:
>> > Hi All
>> >
>> > I'm struggling with a JMeter/HTTPS issue for the past couple of days
>> > and am just short of banging my head against the desk. I searched the
>> > net and found a JMeter patch
>> > (https://issues.apache.org/bugzilla/show_bug.cgi?id=47622) which is
>> > able to record HTTPS requests using the JMeter Proxy Server - and
>> > people have been able to log onto gmail etc. using this patch
>> > (http://www.mail-archive.com/jmeter-dev@jakarta.apache.org/msg19865.html
>> )
>> >
>> > I've downloaded this patch (and the latest nightly build as well -
>> > r894536), and have been trying to replay the script to log on to
>> > gmail. But all I see as the response from the server is the login
>> > screen of gmail. I browsed the mail archive and tried adding an
>> > Authorization Manager, HTTP Cookie Manager to the thread group, but
>> > the ultimate result is the same - on the results tree, most of the
>> > steps (green button - apparently success) show the gmail login screen,
>> > and some of the steps (red marks) return "unauthorized".
>> >
>> > It seems like some session related issue which I'm not able to track
>> > down. Can someone please help me?
>> >
>> > Regards
>> > Arijit
>> >
>> > --
>> > "And when the night is cloudy,
>> > There is still a light that shines on me,
>> > Shine on until tomorrow, let it be."
>> >
>>
>>
>>
>> --
>> "And when the night is cloudy,
>> There is still a light that shines on me,
>> Shine on until tomorrow, let it be."
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>>
>>
>
--
"And when the night is cloudy,
There is still a light that shines on me,
Shine on until tomorrow, let it be."
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: Problem with HTTPS login
Posted by Deepak Shetty <sh...@gmail.com>.
Hi
Gmail uses a lot of dynamically generated variables, unless you sit and
identify each one of these and replace them to be extracted via post
processors, you will get errors.
If GMail is just a test then I suggest you dont use that for writing sample
scripts and use an environment closer to yours.
regards
deepak
On Thu, Jan 7, 2010 at 5:07 AM, Arijit Mukherjee <ar...@gmail.com> wrote:
> A follow-up:
>
> I've been able to record the steps to login to another website
> (www.epw.in) and replay back the script successfully. But it's still a
> no go for gmail. Here's what I have right now:
>
> (1) In jmeter.properties: CookieManager.save.cookies=true
> (2) Added a proxy server to the workbench
> (3) Added a thread-group, and a HTTP Cookie Manager to the thread group
> (4) Proxy Target recording: Test Plant -> Thread Group, rest of the
> options default, started the proxy
> (5) Directed the browser to use JMeter proxy (for all protocols), and
> logged into gmail - script was recorded
> (6) replayed the script - and got back the login page for almost all
> steps, and some "401" errors
>
> It seems if you create the script manually you can add a "URL
> rewriting" element to each of the steps which might work. But for me
> this gmail login is just a test - I am trying to create scripts for
> load testing our server which would involve too many steps to edit
> them manually. We've also tried rerunning a badboy generated script
> and the same thing happens for gmail.
>
> Hoping that someone will be able to throw some light...
>
> Arijit
>
> 2010/1/7 Arijit Mukherjee <ar...@gmail.com>:
> > Hi All
> >
> > I'm struggling with a JMeter/HTTPS issue for the past couple of days
> > and am just short of banging my head against the desk. I searched the
> > net and found a JMeter patch
> > (https://issues.apache.org/bugzilla/show_bug.cgi?id=47622) which is
> > able to record HTTPS requests using the JMeter Proxy Server - and
> > people have been able to log onto gmail etc. using this patch
> > (http://www.mail-archive.com/jmeter-dev@jakarta.apache.org/msg19865.html
> )
> >
> > I've downloaded this patch (and the latest nightly build as well -
> > r894536), and have been trying to replay the script to log on to
> > gmail. But all I see as the response from the server is the login
> > screen of gmail. I browsed the mail archive and tried adding an
> > Authorization Manager, HTTP Cookie Manager to the thread group, but
> > the ultimate result is the same - on the results tree, most of the
> > steps (green button - apparently success) show the gmail login screen,
> > and some of the steps (red marks) return "unauthorized".
> >
> > It seems like some session related issue which I'm not able to track
> > down. Can someone please help me?
> >
> > Regards
> > Arijit
> >
> > --
> > "And when the night is cloudy,
> > There is still a light that shines on me,
> > Shine on until tomorrow, let it be."
> >
>
>
>
> --
> "And when the night is cloudy,
> There is still a light that shines on me,
> Shine on until tomorrow, let it be."
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
Re: Problem with HTTPS login
Posted by Arijit Mukherjee <ar...@gmail.com>.
A follow-up:
I've been able to record the steps to login to another website
(www.epw.in) and replay back the script successfully. But it's still a
no go for gmail. Here's what I have right now:
(1) In jmeter.properties: CookieManager.save.cookies=true
(2) Added a proxy server to the workbench
(3) Added a thread-group, and a HTTP Cookie Manager to the thread group
(4) Proxy Target recording: Test Plant -> Thread Group, rest of the
options default, started the proxy
(5) Directed the browser to use JMeter proxy (for all protocols), and
logged into gmail - script was recorded
(6) replayed the script - and got back the login page for almost all
steps, and some "401" errors
It seems if you create the script manually you can add a "URL
rewriting" element to each of the steps which might work. But for me
this gmail login is just a test - I am trying to create scripts for
load testing our server which would involve too many steps to edit
them manually. We've also tried rerunning a badboy generated script
and the same thing happens for gmail.
Hoping that someone will be able to throw some light...
Arijit
2010/1/7 Arijit Mukherjee <ar...@gmail.com>:
> Hi All
>
> I'm struggling with a JMeter/HTTPS issue for the past couple of days
> and am just short of banging my head against the desk. I searched the
> net and found a JMeter patch
> (https://issues.apache.org/bugzilla/show_bug.cgi?id=47622) which is
> able to record HTTPS requests using the JMeter Proxy Server - and
> people have been able to log onto gmail etc. using this patch
> (http://www.mail-archive.com/jmeter-dev@jakarta.apache.org/msg19865.html)
>
> I've downloaded this patch (and the latest nightly build as well -
> r894536), and have been trying to replay the script to log on to
> gmail. But all I see as the response from the server is the login
> screen of gmail. I browsed the mail archive and tried adding an
> Authorization Manager, HTTP Cookie Manager to the thread group, but
> the ultimate result is the same - on the results tree, most of the
> steps (green button - apparently success) show the gmail login screen,
> and some of the steps (red marks) return "unauthorized".
>
> It seems like some session related issue which I'm not able to track
> down. Can someone please help me?
>
> Regards
> Arijit
>
> --
> "And when the night is cloudy,
> There is still a light that shines on me,
> Shine on until tomorrow, let it be."
>
--
"And when the night is cloudy,
There is still a light that shines on me,
Shine on until tomorrow, let it be."
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org