sebb wrote:
On 01/05/06, Hans L <[EMAIL PROTECTED]> wrote:
Well, no -- there hadn't been anything interesting in there. There was
a "No key found" exception, but that didn't seem to be critical to the
success of the SSL.
Yes, it seems that can be ignored.
The strange thing is that when I created a new JMeter project and
created a single connection test, that seemed to work .... So now I'm
left thinking that perhaps this has to do with the default HTTP request
properties not being propagated down to the individual HTTP Request
samplers ... I'm going to continue testing this tomorrow.
As far as I know, that works in 2.1.1
There is a problem with the Java HTTP Sampler in 2.1.1, which means
that the first SSL request will always fail; this has been fixed in
the nightly build.
Or you could try using the HTTP Client Sampler - this won't work with
expired or untrusted certificates (yet). The nightly build fixes a
problem with cookies.
Thanks for the help. Yes, I am using the nightly build exactly because
of the cookie issue -- took me awhile of mucking through the source
before I finally decided to just try the latest build. My issue is that
my cert for development & QA is self-signed. Following the instructions
posted earlier in the thread, I was able to get that cert trusted in my
keystore. It would be really nice if the documentation in the SSL area
addressed this. I'd be happy to write up what worked for me -- do you
know the official channel for submitting stuff like that?
Thanks,
Hans
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
