On 28/08/07, Christiaan Lamprecht <[EMAIL PROTECTED]> wrote:
> > Except ...
> >
> > This was true for all but the SSL context, which was shared between
> > threads in 2.2 and earlier.
> >
> > Version 2.3RC3 changed the SSL context to be per-thread; however there
> > was a bug that meant some of the
> Except ...
>
> This was true for all but the SSL context, which was shared between
> threads in 2.2 and earlier.
>
> Version 2.3RC3 changed the SSL context to be per-thread; however there
> was a bug that meant some of the objects were recreated too often.
> This has been fixed in the current nig
On 23/08/07, Christiaan Lamprecht <[EMAIL PROTECTED]> wrote:
> On 8/22/07, sebb <[EMAIL PROTECTED]> wrote:
> > JMeter does not do any SSL, other than configuring the connection, so
> > any renegotiation is done by the SSL provider, i.e. by default JSSE in
> > Java 1.4.
>
> Thanks for the quick repl
On 8/22/07, sebb <[EMAIL PROTECTED]> wrote:
> JMeter does not do any SSL, other than configuring the connection, so
> any renegotiation is done by the SSL provider, i.e. by default JSSE in
> Java 1.4.
Thanks for the quick reply. Sounds like good news.
> > There are a few things which can affect h
t; Hi all,
>
> I'm new to JMeter and from the documentation it seems like it can do
> what I need but I would be grateful for some help with a technical
> question.
>
> The question is about how JMeter responds to SSL renegotiation
> requests from the server. So an example w
Hi all,
I'm new to JMeter and from the documentation it seems like it can do
what I need but I would be grateful for some help with a technical
question.
The question is about how JMeter responds to SSL renegotiation
requests from the server. So an example would be; The client sends a
6 matches
Mail list logo
