The documentation says something like this

   - If the browser has already registered a validated certificate for this
   domain, the browser will detect JMeter as a security breach and will refuse
   to load the page. If so, you have to remove the trusted certificate from
   your browser's keystore.

I wonder if it has something to do with this...

Hey

Namaskara~Nalama~Guten Tag~Bonjour


   --
Keigu

Deepak
73500 12833
www.simtree.net, [email protected]
[email protected]

LinkedIn: www.linkedin.com/in/deicool
Skype: thumsupdeicool
Google talk: deicool
Blog: http://loveandfearless.wordpress.com
Facebook: http://www.facebook.com/deicool

"Contribute to the world, environment and more : http://www.gridrepublic.org
"

On Tue, Jun 7, 2016 at 11:37 AM, Deepak Goel <[email protected]> wrote:

> I tried, but same in the error...
>
> If i look at the console, it says...
>
> 16/06/07 11:35:27 INFO  - jmeter.protocol.http.sampler.HTTPHC3Impl: HTTP
> request retry count = 0
> 2016/06/07 11:36:03 WARN  - jmeter.protocol.http.proxy.Proxy: [56172]
> Empty response to http over SSL. Probably waiting for user to authorize the
> certificate for apis.google.com:443
> 2016/06/07 11:36:03 WARN  - jmeter.protocol.http.proxy.Proxy: [56175]
> Empty response to http over SSL. Probably waiting for user to authorize the
> certificate for play.google.com:443
> 2016/06/07 11:36:03 WARN  - jmeter.protocol.http.proxy.Proxy: [56174]
> Empty response to http over SSL. Probably waiting for user to authorize the
> certificate for hangouts.google.com:443
> 2016/06/07 11:36:03 WARN  - jmeter.protocol.http.proxy.Proxy: [56177]
> Empty response to http over SSL. Probably waiting for user to authorize the
> certificate for ssl.gstatic.com:443
> 2016/06/07 11:36:03 WARN  - jmeter.protocol.http.proxy.Proxy: [56171]
> Empty response to http over SSL. Probably waiting for user to authorize the
> certificate for mail.google.com:443
> 2016/06/07 11:36:03 WARN  - jmeter.protocol.http.proxy.Proxy: [56176]
> Empty response to http over SSL. Probably waiting for user to authorize the
> certificate for plus.google.com:443
> 2016/06/07 11:36:03 WARN  - jmeter.protocol.http.proxy.Proxy: [56173]
> Empty response to http over SSL. Probably waiting for user to authorize the
> certificate for clients6.google.com:443
> 2016/06/07 11:36:03 WARN  - jmeter.protocol.http.proxy.Proxy: [56178]
> Empty response to http over SSL. Probably waiting for user to authorize the
> certificate for mail.google.com:443
>
>
> Hey
>
> Namaskara~Nalama~Guten Tag~Bonjour
>
>
>    --
> Keigu
>
> Deepak
> 73500 12833
> www.simtree.net, [email protected]
> [email protected]
>
> LinkedIn: www.linkedin.com/in/deicool
> Skype: thumsupdeicool
> Google talk: deicool
> Blog: http://loveandfearless.wordpress.com
> Facebook: http://www.facebook.com/deicool
>
> "Contribute to the world, environment and more :
> http://www.gridrepublic.org
> "
>
> On Tue, Jun 7, 2016 at 11:31 AM, mahesh bhasme <[email protected]> wrote:
>
>> Hi,
>>
>> Can you change http client version in jmeter while recording.. I think
>> change to http client 3
>> On 6 Jun 2016 22:27, "Deepak Goel" <[email protected]> wrote:
>>
>> > Hey
>> >
>> > Namaskara~Nalama~Guten Tag~Bonjour
>> >
>> > I am trying to record a script in Jmeter using the HTTP(S) Test Script
>> > Recorder. It gives the following error in the browser
>> >
>> > Your connection is not private
>> >
>> > Attackers might be trying to steal your information from *www.xxx.com
>> > <http://www.xxx.com>* (for example, passwords, messages, or credit
>> cards).
>> >
>> > NET::ERR_CERT_AUTHORITY_INVALID
>> >
>> >
>> > Any ideas?
>> >
>> > thanks
>> > Deepak
>> >
>> >    --
>> > Keigu
>> >
>> > Deepak
>> > 73500 12833
>> > www.simtree.net, [email protected]
>> > [email protected]
>> >
>> > LinkedIn: www.linkedin.com/in/deicool
>> > Skype: thumsupdeicool
>> > Google talk: deicool
>> > Blog: http://loveandfearless.wordpress.com
>> > Facebook: http://www.facebook.com/deicool
>> >
>> > "Contribute to the world, environment and more :
>> > http://www.gridrepublic.org
>> > "
>> >
>>
>
>

Reply via email to