I had the intention of writing something to import logs obtained by Daniel Savard's "Live HTTP Headers" extension for Mozilla. This would provide a way to create scripts for HTTP sites -- not perfect (since it would be limited to browsers able to run the extension), but better than nothing.

Unfortunately I've been too busy in recent months, and I don't expect things to change soon, so anyone wanting to take on the idea...

--
Salut,

Jordi.

Peter Lin wrote:
I wouldn't call it a bug. More like an enhancement request.

I generally don't stress test HTTPS, because it's hard to scale
SSL/HTTPS without hardware accelerators. With hardware assistance, the
performance is very close to normal (non-HTTPS) performance.

BigIP is a popular setup for large banks. Basically BigIP handles all
the SSL/HTTPS/encryption and the webservers only do non-encrypted
traffic. which explains why the webservers perform the same.

That's my preference personally, since it makes it easier to test and
much easier to manage. without hardware assistance, SysAdmins resort
to hacks to maintain the webservers. At a previous job, IIS set to
round robin reboot on 15-30minute intervals, because the SSL traffic
would hose windowsNT and IIS.

It's also one of the reasons why win2K and win2K3 have an automatic
restart feature. It's actually used to make sure the server is
restarted ASAP. With Apache, I know plenty of SysAdmins that wrote
PERL scripts to monitor httpd and restart it when it dies under HTTPS
load.

I hope that helps

peter


On Thu, 15 Jul 2004 09:17:41 -0400, joelsherriff <[EMAIL PROTECTED]> wrote:

Peter,

Glad you've pointed this out.  Other tool's proxy servers do this (proxy
SSL) by acting as server to the client and client to the server, decrypting
browser requests and re-encrypting them to forward to the server.  The only
problem is when the client or server insists on being picky about
certificates - but it works for most cases.  I'm trying to find all of the
limitations of jmeter and this is the first entry on my list - that's too
bad.  I wonder if anyone has put any effort into "fixing" this?

J



----- Original Message -----
From: "Peter Lin" <[EMAIL PROTECTED]>
To: "JMeter Users List" <[EMAIL PROTECTED]>
Sent: Thursday, July 15, 2004 8:33 AM
Subject: Re: https url using Jmeter- pls help


I believe the proxy server cannot handle SSL or HTTPS.

if it could, it would mean SSL is not secure. Others have asked the
same question before. you have a couple options.

1. use http and simply change the test plan after you're done
recording. assuming you can still use your web applications in
insecure mode

2. use some other tool

3. manually create the test plan

peter


On Thu, 15 Jul 2004 11:18:17 +0530, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:


hi i am using Jmeter to test a https site i am behind a fire wall and used -u and -a options to connect through the proxy server. it is workig fine for the http url while for https url it is showing a following error: java.io.IOException: Unable to tunnel through 10.200.102.5:8080. Proxy returns "HTTP/1.0 407 Proxy Authentication Required"

if some one has coem acros such a problem previously, please help me
out.
thanks and rgds
Nithya L Nathan

Confidentiality Notice

The information contained in this electronic message and any attachments

to this message are intended

for the exclusive use of the addressee(s) and may contain confidential

or privileged information. If

you are not the intended recipient, please notify the sender at Wipro or

[EMAIL PROTECTED] immediately

and destroy all copies of this message and any attachments.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to