Not able to capture traffic.

[Pravesh Prajapati <pr...@gmail.com>]

Hi Team,
I have a native app using http protocol, but when I try to capture traffice
using Jmeter I am not able to do so.

Please help me.
What change should I make in Properties file so it will work for me.
below is code from property file of jmeter for ssl.
Please help

#---------------------------------------------------------------------------
# SSL configuration
#---------------------------------------------------------------------------

## SSL System properties are now in system.properties

# JMeter no longer converts javax.xxx property entries in this file into
System properties.
# These must now be defined in the system.properties file or on the
command-line.
# The system.properties file gives more flexibility.

# By default, SSL session contexts are now created per-thread, rather than
being shared.
# The original behaviour can be enabled by setting the JMeter property:
#https.sessioncontext.shared=true

# Default HTTPS protocol level:
#https.default.protocol=TLS
# This may need to be changed here (or in user.properties) to:
#https.default.protocol=SSLv3

# List of protocols to enable. You may have to select only a subset if you
find issues with target server.
# This is needed when server does not support Socket version negotiation,
this can lead to:
# javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated
# java.net.SocketException: Connection reset
# see https://issues.apache.org/bugzilla/show_bug.cgi?id=54759
#https.socket.protocols=SSLv2Hello SSLv3 TLSv1

# Control if we allow reuse of cached SSL context between iterations
# set the value to 'false' to reset the SSL context each iteration
#https.use.cached.ssl.context=true

# Start and end index to be used with keystores with many entries
# The default is to use entry 0, i.e. the first
#https.keyStoreStartIndex=0
#https.keyStoreEndIndex=0

-- 
Regards,
Pravesh prajapati.
Mob:-9702600170

Re: Not able to capture traffic.

[Deepak Shetty <sh...@gmail.com>]

In Jmeter you have to start the proxy same as usual as described here
https://jmeter.apache.org/usermanual/jmeter_proxy_step_by_step.pdf
However you do need to configure your native app to use the Proxy and that
depends on your app - some use windows settings -  some like java support
their own command line parameters.

On Fri, Nov 20, 2015 at 7:41 AM, Pravesh Prajapati <
prajapati.pravesh@gmail.com> wrote:

> Hi Team,
> I have a native app using http protocol, but when I try to capture traffice
> using Jmeter I am not able to do so.
>
> Please help me.
> What change should I make in Properties file so it will work for me.
> below is code from property file of jmeter for ssl.
> Please help
>
>
> #---------------------------------------------------------------------------
> # SSL configuration
>
> #---------------------------------------------------------------------------
>
> ## SSL System properties are now in system.properties
>
> # JMeter no longer converts javax.xxx property entries in this file into
> System properties.
> # These must now be defined in the system.properties file or on the
> command-line.
> # The system.properties file gives more flexibility.
>
> # By default, SSL session contexts are now created per-thread, rather than
> being shared.
> # The original behaviour can be enabled by setting the JMeter property:
> #https.sessioncontext.shared=true
>
> # Default HTTPS protocol level:
> #https.default.protocol=TLS
> # This may need to be changed here (or in user.properties) to:
> #https.default.protocol=SSLv3
>
> # List of protocols to enable. You may have to select only a subset if you
> find issues with target server.
> # This is needed when server does not support Socket version negotiation,
> this can lead to:
> # javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated
> # java.net.SocketException: Connection reset
> # see https://issues.apache.org/bugzilla/show_bug.cgi?id=54759
> #https.socket.protocols=SSLv2Hello SSLv3 TLSv1
>
> # Control if we allow reuse of cached SSL context between iterations
> # set the value to 'false' to reset the SSL context each iteration
> #https.use.cached.ssl.context=true
>
> # Start and end index to be used with keystores with many entries
> # The default is to use entry 0, i.e. the first
> #https.keyStoreStartIndex=0
> #https.keyStoreEndIndex=0
>
> --
> Regards,
> Pravesh prajapati.
> Mob:-9702600170
>