You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jmeter.apache.org by Philippe Mouawad <ph...@gmail.com> on 2013/10/01 23:14:10 UTC
JMeter nightly build and recording
Hello,
Testing new Proxy recording on github, I finally managed to record but this
time it was not as easy as for other websites:
I finally succeeded by calling in browser:
- https://ssl.fastly.net and accepting jmeter certificate
- collector.githubapp.com and accepting jmeter certificate
Just adding this in HTTPS Domain was not enough:
github.global.ssl.fastly.net,*.github.com,github.global.ssl.fastly.net,
collector.githubapp.com,ssl.google-analytics.com
Is this what was expected ?
I would have thought accepting JMeter CA would be enough
Am I missing something ?
By the way, before release we need to finish this:
- Document the changes made on JMeter Proxy Server
- Rename it
- Update screenshots for changes and maybe reference documentation
Regards
Philippe
Re: JMeter nightly build and recording
Posted by sebb <se...@gmail.com>.
On 4 October 2013 04:38, Philippe Mouawad <ph...@gmail.com> wrote:
> Hello sebb,
> Do I need to open the ApacheJMeterTemporaryRootCA.crt in Firefox and accept
> it as authority for Websites so that it works ?
Yes, that is what the log message
"Ensure browser is set to accept the JMeter proxy cert"
means. Perhaps it needs to be expanded to show the certificate file name.
> If yes then it works, but it should be documented
That was next on my list.
> and popup that creates
> the proxyservers and shows FingerPrint of Root CA shoud say this.
So what should the pop-up say?
It might be sensible add something to the cert DNAME that identifies
the host on which the certificate was created.
Perhaps the host name and user name?
> If not then it is not working for me.
>
> Regards
> Philippe
>
>
> On Fri, Oct 4, 2013 at 4:54 AM, Philippe Mouawad <philippe.mouawad@gmail.com
>> wrote:
>
>> Hello sebb,
>> Gave it another try, still have to manually enter URL for
>> github.global.ssl.fastly.net and accept certificate, same for
>> collector.githubapp.com'
>> I am using FF 24.0 on Mac OSX 10.6.8 or 10.8.5
>>
>> By the way I noticed another potential issue, If I hard code java path to
>> a jdk7 but don't set JAVA_HOME to it, then keytool runs with JDK6 (because
>> it's the one in the path), should we check this ?
>>
>> Logs:
>> 2013/10/04 04:41:14 WARN - jmeter.protocol.http.proxy.ProxyControl: Could
>> not open/read key store
>> /data/decathlon/workspace/jmeter/bin/proxyserver.jks (No such file or
>> directory)
>> 2013/10/04 04:41:14 INFO - jmeter.protocol.http.proxy.ProxyControl:
>> Creating Proxy CA in /data/decathlon/workspace/jmeter/bin/proxyserver.jks
>> 2013/10/04 04:41:17 INFO - jmeter.protocol.http.proxy.ProxyControl:
>> Created keystore in /data/decathlon/workspace/jmeter/bin/proxyserver.jks
>> 2013/10/04 04:41:17 INFO - jmeter.protocol.http.proxy.ProxyControl:
>> Creating entry github.global.ssl.fastly.net in
>> /data/decathlon/workspace/jmeter/bin/proxyserver.jks
>> 2013/10/04 04:41:19 INFO - jmeter.protocol.http.proxy.ProxyControl:
>> Creating entry github.com in
>> /data/decathlon/workspace/jmeter/bin/proxyserver.jks
>> 2013/10/04 04:41:21 INFO - jmeter.protocol.http.proxy.Daemon: Creating
>> Daemon Socket on port: 8888
>> 2013/10/04 04:41:21 INFO - jmeter.protocol.http.proxy.Daemon: Proxy up
>> and running!
>> 2013/10/04 04:41:33 INFO - jmeter.protocol.http.proxy.ProxyControl:
>> [53076] Creating entry www.google.com in
>> /data/decathlon/workspace/jmeter/bin/proxyserver.jks
>> 2013/10/04 04:41:36 WARN - jmeter.protocol.http.proxy.Proxy: [53076]
>> Problem with SSL certificate for 'www.google.com'? Ensure browser is set
>> to accept the JMeter proxy cert: Received fatal alert: unknown_ca
>> 2013/10/04 04:41:43 WARN - jmeter.protocol.http.proxy.Proxy: [53077]
>> Problem with SSL certificate for 'github.com'? Ensure browser is set to
>> accept the JMeter proxy cert: Received fatal alert: unknown_ca
>> 2013/10/04 04:41:47 WARN - jmeter.protocol.http.proxy.Proxy: [53078]
>> Problem with SSL certificate for 'github.com'? Ensure browser is set to
>> accept the JMeter proxy cert: Received fatal alert: unknown_ca
>> 2013/10/04 04:41:50 WARN - jmeter.protocol.http.proxy.Proxy: [53082]
>> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>> unknown_ca
>> 2013/10/04 04:41:50 WARN - jmeter.protocol.http.proxy.Proxy: [53088]
>> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>> unknown_ca
>> 2013/10/04 04:41:50 WARN - jmeter.protocol.http.proxy.Proxy: [53086]
>> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>> unknown_ca
>> 2013/10/04 04:41:50 WARN - jmeter.protocol.http.proxy.Proxy: [53087]
>> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>> unknown_ca
>> 2013/10/04 04:44:37 WARN - jmeter.protocol.http.proxy.Proxy: [53108]
>> Problem with SSL certificate for 'github.com'? Ensure browser is set to
>> accept the JMeter proxy cert: Received fatal alert: unknown_ca
>> 2013/10/04 04:44:42 WARN - jmeter.protocol.http.proxy.Proxy: [53109]
>> Problem with SSL certificate for 'github.com'? Ensure browser is set to
>> accept the JMeter proxy cert: Received fatal alert: unknown_ca
>> 2013/10/04 04:44:45 WARN - jmeter.protocol.http.proxy.Proxy: [53112]
>> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>> unknown_ca
>> 2013/10/04 04:44:45 WARN - jmeter.protocol.http.proxy.Proxy: [53114]
>> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>> unknown_ca
>> 2013/10/04 04:44:45 WARN - jmeter.protocol.http.proxy.Proxy: [53116]
>> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>> unknown_ca
>> 2013/10/04 04:44:45 WARN - jmeter.protocol.http.proxy.Proxy: [53115]
>> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>> unknown_ca
>> 2013/10/04 04:44:45 WARN - jmeter.protocol.http.proxy.Proxy: [53117]
>> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>> unknown_ca
>> 2013/10/04 04:44:58 WARN - jmeter.protocol.http.proxy.Proxy: [53132]
>> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>> unknown_ca
>> 2013/10/04 04:44:58 WARN - jmeter.protocol.http.proxy.Proxy: [53134]
>> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>> unknown_ca
>> 2013/10/04 04:44:58 WARN - jmeter.protocol.http.proxy.Proxy: [53135]
>> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>> unknown_ca
>> 2013/10/04 04:44:58 WARN - jmeter.protocol.http.proxy.Proxy: [53136]
>> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>> unknown_ca
>> 2013/10/04 04:45:11 WARN - jmeter.protocol.http.proxy.Proxy: [53148]
>> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>> unknown_ca
>> 2013/10/04 04:45:15 WARN - jmeter.protocol.http.proxy.Proxy: [53149]
>> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>> unknown_ca
>> 2013/10/04 04:45:27 WARN - jmeter.protocol.http.proxy.Proxy: [53165]
>> Problem with SSL certificate for 'ssl.google-analytics.com'? Ensure
>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>> unknown_ca
>> 2013/10/04 04:45:28 WARN - jmeter.protocol.http.proxy.Proxy: [53160]
>> Empty request, ignored
>> 2013/10/04 04:45:29 WARN - jmeter.protocol.http.proxy.Proxy: [53167]
>> Problem with SSL certificate for 'collector.githubapp.com'? Ensure
>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>> unknown_ca
>>
>>
>> Regards
>> Philippe
>>
>>
>>
>>
>> On Thu, Oct 3, 2013 at 7:05 PM, sebb <se...@gmail.com> wrote:
>>
>>> On 3 October 2013 14:28, Philippe Mouawad <ph...@gmail.com>
>>> wrote:
>>> > Hello sebb,
>>> > You can do the test just call https://github.com
>>>
>>> I had some problems initially, but after removing proxyserver.jks it
>>> all seems to work OK.
>>>
>>> I've updated the code with better logging; also the validity of the
>>> root CA is now checked.
>>>
>>> Please try again.
>>>
>>> > Regards
>>> > Philippe
>>> >
>>> >
>>> > On Thu, Oct 3, 2013 at 2:45 PM, sebb <se...@gmail.com> wrote:
>>> >
>>> >> On 1 October 2013 22:14, Philippe Mouawad <ph...@gmail.com>
>>> >> wrote:
>>> >> > Hello,
>>> >> > Testing new Proxy recording on github, I finally managed to record
>>> but
>>> >> this
>>> >> > time it was not as easy as for other websites:
>>> >> >
>>> >> > I finally succeeded by calling in browser:
>>> >> > - https://ssl.fastly.net and accepting jmeter certificate
>>> >> > - collector.githubapp.com and accepting jmeter certificate
>>> >> >
>>> >> > Just adding this in HTTPS Domain was not enough:
>>> >> > github.global.ssl.fastly.net,*.github.com,
>>> github.global.ssl.fastly.net,
>>> >> > collector.githubapp.com,ssl.google-analytics.com
>>> >>
>>> >> Why not use domains for them all?
>>> >>
>>> >> *.fastly.net
>>> >> *.github.com
>>> >> *.githubapp.com
>>> >> *.google-analytics.com
>>> >>
>>> >> > Is this what was expected ?
>>> >> > I would have thought accepting JMeter CA would be enough
>>> >> >
>>> >> > Am I missing something ?
>>> >>
>>> >> Presumably.
>>> >>
>>> >> What URLs did you visit?
>>> >>
>>> >> What does the jmeter log say?
>>> >> It should report warnings for missing certificates; if no extra logs
>>> >> or changed levels may be needed.
>>> >>
>>> >> > By the way, before release we need to finish this:
>>> >> > - Document the changes made on JMeter Proxy Server
>>> >> > - Rename it
>>> >> > - Update screenshots for changes and maybe reference documentation
>>> >> >
>>> >> > Regards
>>> >> > Philippe
>>> >>
>>> >
>>> >
>>> >
>>> > --
>>> > Cordialement.
>>> > Philippe Mouawad.
>>>
>>
>>
>>
>> --
>> Cordialement.
>> Philippe Mouawad.
>>
>>
>>
>
>
> --
> Cordialement.
> Philippe Mouawad.
Re: JMeter nightly build and recording
Posted by Philippe Mouawad <ph...@gmail.com>.
Hello sebb,
I would like the popup say something like:
- A ApacheJMeterTemporaryRootCA.crt has been generated in bin folder,
ensure you install it in your browser before starting the recording session.
- Add a link to component reference pointing to the paragraph that
describes how to install a certificate in Browser
- Maybe even provide a way to click to install ?
This way user doesn't have to find the documentation block and will from
the start have a good recording session.
And it will be much easier for newbies.
Also I suggest we recommand to use JDK7 with JMeter even if we keep
compatibility.
Because I really think the job you made on this feature is GREAT ! Without
flattering you :-)
The only last point is we need to make it cristal clear, for me it is not
yet. As I told you , trying to be as stupid as I can (I can be very much)
It was not clear for me that I had to install the CRT.
Once done , wow recording HTTPS becomes so simple !
Regards
Philippe
On Tue, Oct 8, 2013 at 5:15 PM, sebb <se...@gmail.com> wrote:
> On 7 October 2013 20:55, Philippe Mouawad <ph...@gmail.com>
> wrote:
> > Hello sebb,
> > I have tested last nightly build, I was wondering why we don't put the
> info
> > on loading the crt file in browser in the popup that is shown when you
> > start proxy, I mean this paragraph :
> > Installing the JMeter CA certificate for HTTPS recording
>
> Not sure what you mean exactly.
> What text would you like to see in the pop-up?
>
> >
> > Also regarding documentation. Why not put 2.10 block on top and all
> > remaining 2.9 method below (just before control panel).
> >
> > Because currently user has to read a lot of documentation, while with all
> > the improvements you made it is rather really easy with 2.10.
>
> OK, I'll see what I can do.
>
> > Regards
> >
> >
> >
> > On Fri, Oct 4, 2013 at 5:38 AM, Philippe Mouawad <
> philippe.mouawad@gmail.com
> >> wrote:
> >
> >> Hello sebb,
> >> Do I need to open the ApacheJMeterTemporaryRootCA.crt in Firefox and
> >> accept it as authority for Websites so that it works ?
> >> If yes then it works, but it should be documented and popup that creates
> >> the proxyservers and shows FingerPrint of Root CA shoud say this.
> >> If not then it is not working for me.
> >>
> >> Regards
> >> Philippe
> >>
> >>
> >> On Fri, Oct 4, 2013 at 4:54 AM, Philippe Mouawad <
> >> philippe.mouawad@gmail.com> wrote:
> >>
> >>> Hello sebb,
> >>> Gave it another try, still have to manually enter URL for
> >>> github.global.ssl.fastly.net and accept certificate, same for
> >>> collector.githubapp.com'
> >>> I am using FF 24.0 on Mac OSX 10.6.8 or 10.8.5
> >>>
> >>> By the way I noticed another potential issue, If I hard code java path
> to
> >>> a jdk7 but don't set JAVA_HOME to it, then keytool runs with JDK6
> (because
> >>> it's the one in the path), should we check this ?
> >>>
> >>> Logs:
> >>> 2013/10/04 04:41:14 WARN - jmeter.protocol.http.proxy.ProxyControl:
> >>> Could not open/read key store
> >>> /data/decathlon/workspace/jmeter/bin/proxyserver.jks (No such file or
> >>> directory)
> >>> 2013/10/04 04:41:14 INFO - jmeter.protocol.http.proxy.ProxyControl:
> >>> Creating Proxy CA in
> /data/decathlon/workspace/jmeter/bin/proxyserver.jks
> >>> 2013/10/04 04:41:17 INFO - jmeter.protocol.http.proxy.ProxyControl:
> >>> Created keystore in
> /data/decathlon/workspace/jmeter/bin/proxyserver.jks
> >>> 2013/10/04 04:41:17 INFO - jmeter.protocol.http.proxy.ProxyControl:
> >>> Creating entry github.global.ssl.fastly.net in
> >>> /data/decathlon/workspace/jmeter/bin/proxyserver.jks
> >>> 2013/10/04 04:41:19 INFO - jmeter.protocol.http.proxy.ProxyControl:
> >>> Creating entry github.com in
> >>> /data/decathlon/workspace/jmeter/bin/proxyserver.jks
> >>> 2013/10/04 04:41:21 INFO - jmeter.protocol.http.proxy.Daemon: Creating
> >>> Daemon Socket on port: 8888
> >>> 2013/10/04 04:41:21 INFO - jmeter.protocol.http.proxy.Daemon: Proxy up
> >>> and running!
> >>> 2013/10/04 04:41:33 INFO - jmeter.protocol.http.proxy.ProxyControl:
> >>> [53076] Creating entry www.google.com in
> >>> /data/decathlon/workspace/jmeter/bin/proxyserver.jks
> >>> 2013/10/04 04:41:36 WARN - jmeter.protocol.http.proxy.Proxy: [53076]
> >>> Problem with SSL certificate for 'www.google.com'? Ensure browser is
> set
> >>> to accept the JMeter proxy cert: Received fatal alert: unknown_ca
> >>> 2013/10/04 04:41:43 WARN - jmeter.protocol.http.proxy.Proxy: [53077]
> >>> Problem with SSL certificate for 'github.com'? Ensure browser is set
> to
> >>> accept the JMeter proxy cert: Received fatal alert: unknown_ca
> >>> 2013/10/04 04:41:47 WARN - jmeter.protocol.http.proxy.Proxy: [53078]
> >>> Problem with SSL certificate for 'github.com'? Ensure browser is set
> to
> >>> accept the JMeter proxy cert: Received fatal alert: unknown_ca
> >>> 2013/10/04 04:41:50 WARN - jmeter.protocol.http.proxy.Proxy: [53082]
> >>> Problem with SSL certificate for 'github.global.ssl.fastly.net'?
> Ensure
> >>> browser is set to accept the JMeter proxy cert: Received fatal alert:
> >>> unknown_ca
> >>> 2013/10/04 04:41:50 WARN - jmeter.protocol.http.proxy.Proxy: [53088]
> >>> Problem with SSL certificate for 'github.global.ssl.fastly.net'?
> Ensure
> >>> browser is set to accept the JMeter proxy cert: Received fatal alert:
> >>> unknown_ca
> >>> 2013/10/04 04:41:50 WARN - jmeter.protocol.http.proxy.Proxy: [53086]
> >>> Problem with SSL certificate for 'github.global.ssl.fastly.net'?
> Ensure
> >>> browser is set to accept the JMeter proxy cert: Received fatal alert:
> >>> unknown_ca
> >>> 2013/10/04 04:41:50 WARN - jmeter.protocol.http.proxy.Proxy: [53087]
> >>> Problem with SSL certificate for 'github.global.ssl.fastly.net'?
> Ensure
> >>> browser is set to accept the JMeter proxy cert: Received fatal alert:
> >>> unknown_ca
> >>> 2013/10/04 04:44:37 WARN - jmeter.protocol.http.proxy.Proxy: [53108]
> >>> Problem with SSL certificate for 'github.com'? Ensure browser is set
> to
> >>> accept the JMeter proxy cert: Received fatal alert: unknown_ca
> >>> 2013/10/04 04:44:42 WARN - jmeter.protocol.http.proxy.Proxy: [53109]
> >>> Problem with SSL certificate for 'github.com'? Ensure browser is set
> to
> >>> accept the JMeter proxy cert: Received fatal alert: unknown_ca
> >>> 2013/10/04 04:44:45 WARN - jmeter.protocol.http.proxy.Proxy: [53112]
> >>> Problem with SSL certificate for 'github.global.ssl.fastly.net'?
> Ensure
> >>> browser is set to accept the JMeter proxy cert: Received fatal alert:
> >>> unknown_ca
> >>> 2013/10/04 04:44:45 WARN - jmeter.protocol.http.proxy.Proxy: [53114]
> >>> Problem with SSL certificate for 'github.global.ssl.fastly.net'?
> Ensure
> >>> browser is set to accept the JMeter proxy cert: Received fatal alert:
> >>> unknown_ca
> >>> 2013/10/04 04:44:45 WARN - jmeter.protocol.http.proxy.Proxy: [53116]
> >>> Problem with SSL certificate for 'github.global.ssl.fastly.net'?
> Ensure
> >>> browser is set to accept the JMeter proxy cert: Received fatal alert:
> >>> unknown_ca
> >>> 2013/10/04 04:44:45 WARN - jmeter.protocol.http.proxy.Proxy: [53115]
> >>> Problem with SSL certificate for 'github.global.ssl.fastly.net'?
> Ensure
> >>> browser is set to accept the JMeter proxy cert: Received fatal alert:
> >>> unknown_ca
> >>> 2013/10/04 04:44:45 WARN - jmeter.protocol.http.proxy.Proxy: [53117]
> >>> Problem with SSL certificate for 'github.global.ssl.fastly.net'?
> Ensure
> >>> browser is set to accept the JMeter proxy cert: Received fatal alert:
> >>> unknown_ca
> >>> 2013/10/04 04:44:58 WARN - jmeter.protocol.http.proxy.Proxy: [53132]
> >>> Problem with SSL certificate for 'github.global.ssl.fastly.net'?
> Ensure
> >>> browser is set to accept the JMeter proxy cert: Received fatal alert:
> >>> unknown_ca
> >>> 2013/10/04 04:44:58 WARN - jmeter.protocol.http.proxy.Proxy: [53134]
> >>> Problem with SSL certificate for 'github.global.ssl.fastly.net'?
> Ensure
> >>> browser is set to accept the JMeter proxy cert: Received fatal alert:
> >>> unknown_ca
> >>> 2013/10/04 04:44:58 WARN - jmeter.protocol.http.proxy.Proxy: [53135]
> >>> Problem with SSL certificate for 'github.global.ssl.fastly.net'?
> Ensure
> >>> browser is set to accept the JMeter proxy cert: Received fatal alert:
> >>> unknown_ca
> >>> 2013/10/04 04:44:58 WARN - jmeter.protocol.http.proxy.Proxy: [53136]
> >>> Problem with SSL certificate for 'github.global.ssl.fastly.net'?
> Ensure
> >>> browser is set to accept the JMeter proxy cert: Received fatal alert:
> >>> unknown_ca
> >>> 2013/10/04 04:45:11 WARN - jmeter.protocol.http.proxy.Proxy: [53148]
> >>> Problem with SSL certificate for 'github.global.ssl.fastly.net'?
> Ensure
> >>> browser is set to accept the JMeter proxy cert: Received fatal alert:
> >>> unknown_ca
> >>> 2013/10/04 04:45:15 WARN - jmeter.protocol.http.proxy.Proxy: [53149]
> >>> Problem with SSL certificate for 'github.global.ssl.fastly.net'?
> Ensure
> >>> browser is set to accept the JMeter proxy cert: Received fatal alert:
> >>> unknown_ca
> >>> 2013/10/04 04:45:27 WARN - jmeter.protocol.http.proxy.Proxy: [53165]
> >>> Problem with SSL certificate for 'ssl.google-analytics.com'? Ensure
> >>> browser is set to accept the JMeter proxy cert: Received fatal alert:
> >>> unknown_ca
> >>> 2013/10/04 04:45:28 WARN - jmeter.protocol.http.proxy.Proxy: [53160]
> >>> Empty request, ignored
> >>> 2013/10/04 04:45:29 WARN - jmeter.protocol.http.proxy.Proxy: [53167]
> >>> Problem with SSL certificate for 'collector.githubapp.com'? Ensure
> >>> browser is set to accept the JMeter proxy cert: Received fatal alert:
> >>> unknown_ca
> >>>
> >>>
> >>> Regards
> >>> Philippe
> >>>
> >>>
> >>>
> >>>
> >>> On Thu, Oct 3, 2013 at 7:05 PM, sebb <se...@gmail.com> wrote:
> >>>
> >>>> On 3 October 2013 14:28, Philippe Mouawad <philippe.mouawad@gmail.com
> >
> >>>> wrote:
> >>>> > Hello sebb,
> >>>> > You can do the test just call https://github.com
> >>>>
> >>>> I had some problems initially, but after removing proxyserver.jks it
> >>>> all seems to work OK.
> >>>>
> >>>> I've updated the code with better logging; also the validity of the
> >>>> root CA is now checked.
> >>>>
> >>>> Please try again.
> >>>>
> >>>> > Regards
> >>>> > Philippe
> >>>> >
> >>>> >
> >>>> > On Thu, Oct 3, 2013 at 2:45 PM, sebb <se...@gmail.com> wrote:
> >>>> >
> >>>> >> On 1 October 2013 22:14, Philippe Mouawad <
> philippe.mouawad@gmail.com
> >>>> >
> >>>> >> wrote:
> >>>> >> > Hello,
> >>>> >> > Testing new Proxy recording on github, I finally managed to
> record
> >>>> but
> >>>> >> this
> >>>> >> > time it was not as easy as for other websites:
> >>>> >> >
> >>>> >> > I finally succeeded by calling in browser:
> >>>> >> > - https://ssl.fastly.net and accepting jmeter certificate
> >>>> >> > - collector.githubapp.com and accepting jmeter certificate
> >>>> >> >
> >>>> >> > Just adding this in HTTPS Domain was not enough:
> >>>> >> > github.global.ssl.fastly.net,*.github.com,
> >>>> github.global.ssl.fastly.net,
> >>>> >> > collector.githubapp.com,ssl.google-analytics.com
> >>>> >>
> >>>> >> Why not use domains for them all?
> >>>> >>
> >>>> >> *.fastly.net
> >>>> >> *.github.com
> >>>> >> *.githubapp.com
> >>>> >> *.google-analytics.com
> >>>> >>
> >>>> >> > Is this what was expected ?
> >>>> >> > I would have thought accepting JMeter CA would be enough
> >>>> >> >
> >>>> >> > Am I missing something ?
> >>>> >>
> >>>> >> Presumably.
> >>>> >>
> >>>> >> What URLs did you visit?
> >>>> >>
> >>>> >> What does the jmeter log say?
> >>>> >> It should report warnings for missing certificates; if no extra
> logs
> >>>> >> or changed levels may be needed.
> >>>> >>
> >>>> >> > By the way, before release we need to finish this:
> >>>> >> > - Document the changes made on JMeter Proxy Server
> >>>> >> > - Rename it
> >>>> >> > - Update screenshots for changes and maybe reference
> documentation
> >>>> >> >
> >>>> >> > Regards
> >>>> >> > Philippe
> >>>> >>
> >>>> >
> >>>> >
> >>>> >
> >>>> > --
> >>>> > Cordialement.
> >>>> > Philippe Mouawad.
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>> Cordialement.
> >>> Philippe Mouawad.
> >>>
> >>>
> >>>
> >>
> >>
> >> --
> >> Cordialement.
> >> Philippe Mouawad.
> >>
> >>
> >>
> >
> >
> > --
> > Cordialement.
> > Philippe Mouawad.
>
--
Cordialement.
Philippe Mouawad.
Re: JMeter nightly build and recording
Posted by sebb <se...@gmail.com>.
On 7 October 2013 20:55, Philippe Mouawad <ph...@gmail.com> wrote:
> Hello sebb,
> I have tested last nightly build, I was wondering why we don't put the info
> on loading the crt file in browser in the popup that is shown when you
> start proxy, I mean this paragraph :
> Installing the JMeter CA certificate for HTTPS recording
Not sure what you mean exactly.
What text would you like to see in the pop-up?
>
> Also regarding documentation. Why not put 2.10 block on top and all
> remaining 2.9 method below (just before control panel).
>
> Because currently user has to read a lot of documentation, while with all
> the improvements you made it is rather really easy with 2.10.
OK, I'll see what I can do.
> Regards
>
>
>
> On Fri, Oct 4, 2013 at 5:38 AM, Philippe Mouawad <philippe.mouawad@gmail.com
>> wrote:
>
>> Hello sebb,
>> Do I need to open the ApacheJMeterTemporaryRootCA.crt in Firefox and
>> accept it as authority for Websites so that it works ?
>> If yes then it works, but it should be documented and popup that creates
>> the proxyservers and shows FingerPrint of Root CA shoud say this.
>> If not then it is not working for me.
>>
>> Regards
>> Philippe
>>
>>
>> On Fri, Oct 4, 2013 at 4:54 AM, Philippe Mouawad <
>> philippe.mouawad@gmail.com> wrote:
>>
>>> Hello sebb,
>>> Gave it another try, still have to manually enter URL for
>>> github.global.ssl.fastly.net and accept certificate, same for
>>> collector.githubapp.com'
>>> I am using FF 24.0 on Mac OSX 10.6.8 or 10.8.5
>>>
>>> By the way I noticed another potential issue, If I hard code java path to
>>> a jdk7 but don't set JAVA_HOME to it, then keytool runs with JDK6 (because
>>> it's the one in the path), should we check this ?
>>>
>>> Logs:
>>> 2013/10/04 04:41:14 WARN - jmeter.protocol.http.proxy.ProxyControl:
>>> Could not open/read key store
>>> /data/decathlon/workspace/jmeter/bin/proxyserver.jks (No such file or
>>> directory)
>>> 2013/10/04 04:41:14 INFO - jmeter.protocol.http.proxy.ProxyControl:
>>> Creating Proxy CA in /data/decathlon/workspace/jmeter/bin/proxyserver.jks
>>> 2013/10/04 04:41:17 INFO - jmeter.protocol.http.proxy.ProxyControl:
>>> Created keystore in /data/decathlon/workspace/jmeter/bin/proxyserver.jks
>>> 2013/10/04 04:41:17 INFO - jmeter.protocol.http.proxy.ProxyControl:
>>> Creating entry github.global.ssl.fastly.net in
>>> /data/decathlon/workspace/jmeter/bin/proxyserver.jks
>>> 2013/10/04 04:41:19 INFO - jmeter.protocol.http.proxy.ProxyControl:
>>> Creating entry github.com in
>>> /data/decathlon/workspace/jmeter/bin/proxyserver.jks
>>> 2013/10/04 04:41:21 INFO - jmeter.protocol.http.proxy.Daemon: Creating
>>> Daemon Socket on port: 8888
>>> 2013/10/04 04:41:21 INFO - jmeter.protocol.http.proxy.Daemon: Proxy up
>>> and running!
>>> 2013/10/04 04:41:33 INFO - jmeter.protocol.http.proxy.ProxyControl:
>>> [53076] Creating entry www.google.com in
>>> /data/decathlon/workspace/jmeter/bin/proxyserver.jks
>>> 2013/10/04 04:41:36 WARN - jmeter.protocol.http.proxy.Proxy: [53076]
>>> Problem with SSL certificate for 'www.google.com'? Ensure browser is set
>>> to accept the JMeter proxy cert: Received fatal alert: unknown_ca
>>> 2013/10/04 04:41:43 WARN - jmeter.protocol.http.proxy.Proxy: [53077]
>>> Problem with SSL certificate for 'github.com'? Ensure browser is set to
>>> accept the JMeter proxy cert: Received fatal alert: unknown_ca
>>> 2013/10/04 04:41:47 WARN - jmeter.protocol.http.proxy.Proxy: [53078]
>>> Problem with SSL certificate for 'github.com'? Ensure browser is set to
>>> accept the JMeter proxy cert: Received fatal alert: unknown_ca
>>> 2013/10/04 04:41:50 WARN - jmeter.protocol.http.proxy.Proxy: [53082]
>>> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
>>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>>> unknown_ca
>>> 2013/10/04 04:41:50 WARN - jmeter.protocol.http.proxy.Proxy: [53088]
>>> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
>>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>>> unknown_ca
>>> 2013/10/04 04:41:50 WARN - jmeter.protocol.http.proxy.Proxy: [53086]
>>> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
>>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>>> unknown_ca
>>> 2013/10/04 04:41:50 WARN - jmeter.protocol.http.proxy.Proxy: [53087]
>>> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
>>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>>> unknown_ca
>>> 2013/10/04 04:44:37 WARN - jmeter.protocol.http.proxy.Proxy: [53108]
>>> Problem with SSL certificate for 'github.com'? Ensure browser is set to
>>> accept the JMeter proxy cert: Received fatal alert: unknown_ca
>>> 2013/10/04 04:44:42 WARN - jmeter.protocol.http.proxy.Proxy: [53109]
>>> Problem with SSL certificate for 'github.com'? Ensure browser is set to
>>> accept the JMeter proxy cert: Received fatal alert: unknown_ca
>>> 2013/10/04 04:44:45 WARN - jmeter.protocol.http.proxy.Proxy: [53112]
>>> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
>>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>>> unknown_ca
>>> 2013/10/04 04:44:45 WARN - jmeter.protocol.http.proxy.Proxy: [53114]
>>> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
>>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>>> unknown_ca
>>> 2013/10/04 04:44:45 WARN - jmeter.protocol.http.proxy.Proxy: [53116]
>>> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
>>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>>> unknown_ca
>>> 2013/10/04 04:44:45 WARN - jmeter.protocol.http.proxy.Proxy: [53115]
>>> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
>>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>>> unknown_ca
>>> 2013/10/04 04:44:45 WARN - jmeter.protocol.http.proxy.Proxy: [53117]
>>> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
>>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>>> unknown_ca
>>> 2013/10/04 04:44:58 WARN - jmeter.protocol.http.proxy.Proxy: [53132]
>>> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
>>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>>> unknown_ca
>>> 2013/10/04 04:44:58 WARN - jmeter.protocol.http.proxy.Proxy: [53134]
>>> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
>>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>>> unknown_ca
>>> 2013/10/04 04:44:58 WARN - jmeter.protocol.http.proxy.Proxy: [53135]
>>> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
>>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>>> unknown_ca
>>> 2013/10/04 04:44:58 WARN - jmeter.protocol.http.proxy.Proxy: [53136]
>>> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
>>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>>> unknown_ca
>>> 2013/10/04 04:45:11 WARN - jmeter.protocol.http.proxy.Proxy: [53148]
>>> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
>>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>>> unknown_ca
>>> 2013/10/04 04:45:15 WARN - jmeter.protocol.http.proxy.Proxy: [53149]
>>> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
>>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>>> unknown_ca
>>> 2013/10/04 04:45:27 WARN - jmeter.protocol.http.proxy.Proxy: [53165]
>>> Problem with SSL certificate for 'ssl.google-analytics.com'? Ensure
>>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>>> unknown_ca
>>> 2013/10/04 04:45:28 WARN - jmeter.protocol.http.proxy.Proxy: [53160]
>>> Empty request, ignored
>>> 2013/10/04 04:45:29 WARN - jmeter.protocol.http.proxy.Proxy: [53167]
>>> Problem with SSL certificate for 'collector.githubapp.com'? Ensure
>>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>>> unknown_ca
>>>
>>>
>>> Regards
>>> Philippe
>>>
>>>
>>>
>>>
>>> On Thu, Oct 3, 2013 at 7:05 PM, sebb <se...@gmail.com> wrote:
>>>
>>>> On 3 October 2013 14:28, Philippe Mouawad <ph...@gmail.com>
>>>> wrote:
>>>> > Hello sebb,
>>>> > You can do the test just call https://github.com
>>>>
>>>> I had some problems initially, but after removing proxyserver.jks it
>>>> all seems to work OK.
>>>>
>>>> I've updated the code with better logging; also the validity of the
>>>> root CA is now checked.
>>>>
>>>> Please try again.
>>>>
>>>> > Regards
>>>> > Philippe
>>>> >
>>>> >
>>>> > On Thu, Oct 3, 2013 at 2:45 PM, sebb <se...@gmail.com> wrote:
>>>> >
>>>> >> On 1 October 2013 22:14, Philippe Mouawad <philippe.mouawad@gmail.com
>>>> >
>>>> >> wrote:
>>>> >> > Hello,
>>>> >> > Testing new Proxy recording on github, I finally managed to record
>>>> but
>>>> >> this
>>>> >> > time it was not as easy as for other websites:
>>>> >> >
>>>> >> > I finally succeeded by calling in browser:
>>>> >> > - https://ssl.fastly.net and accepting jmeter certificate
>>>> >> > - collector.githubapp.com and accepting jmeter certificate
>>>> >> >
>>>> >> > Just adding this in HTTPS Domain was not enough:
>>>> >> > github.global.ssl.fastly.net,*.github.com,
>>>> github.global.ssl.fastly.net,
>>>> >> > collector.githubapp.com,ssl.google-analytics.com
>>>> >>
>>>> >> Why not use domains for them all?
>>>> >>
>>>> >> *.fastly.net
>>>> >> *.github.com
>>>> >> *.githubapp.com
>>>> >> *.google-analytics.com
>>>> >>
>>>> >> > Is this what was expected ?
>>>> >> > I would have thought accepting JMeter CA would be enough
>>>> >> >
>>>> >> > Am I missing something ?
>>>> >>
>>>> >> Presumably.
>>>> >>
>>>> >> What URLs did you visit?
>>>> >>
>>>> >> What does the jmeter log say?
>>>> >> It should report warnings for missing certificates; if no extra logs
>>>> >> or changed levels may be needed.
>>>> >>
>>>> >> > By the way, before release we need to finish this:
>>>> >> > - Document the changes made on JMeter Proxy Server
>>>> >> > - Rename it
>>>> >> > - Update screenshots for changes and maybe reference documentation
>>>> >> >
>>>> >> > Regards
>>>> >> > Philippe
>>>> >>
>>>> >
>>>> >
>>>> >
>>>> > --
>>>> > Cordialement.
>>>> > Philippe Mouawad.
>>>>
>>>
>>>
>>>
>>> --
>>> Cordialement.
>>> Philippe Mouawad.
>>>
>>>
>>>
>>
>>
>> --
>> Cordialement.
>> Philippe Mouawad.
>>
>>
>>
>
>
> --
> Cordialement.
> Philippe Mouawad.
Re: JMeter nightly build and recording
Posted by Philippe Mouawad <ph...@gmail.com>.
Hello sebb,
I have tested last nightly build, I was wondering why we don't put the info
on loading the crt file in browser in the popup that is shown when you
start proxy, I mean this paragraph :
Installing the JMeter CA certificate for HTTPS recording
Also regarding documentation. Why not put 2.10 block on top and all
remaining 2.9 method below (just before control panel).
Because currently user has to read a lot of documentation, while with all
the improvements you made it is rather really easy with 2.10.
Regards
On Fri, Oct 4, 2013 at 5:38 AM, Philippe Mouawad <philippe.mouawad@gmail.com
> wrote:
> Hello sebb,
> Do I need to open the ApacheJMeterTemporaryRootCA.crt in Firefox and
> accept it as authority for Websites so that it works ?
> If yes then it works, but it should be documented and popup that creates
> the proxyservers and shows FingerPrint of Root CA shoud say this.
> If not then it is not working for me.
>
> Regards
> Philippe
>
>
> On Fri, Oct 4, 2013 at 4:54 AM, Philippe Mouawad <
> philippe.mouawad@gmail.com> wrote:
>
>> Hello sebb,
>> Gave it another try, still have to manually enter URL for
>> github.global.ssl.fastly.net and accept certificate, same for
>> collector.githubapp.com'
>> I am using FF 24.0 on Mac OSX 10.6.8 or 10.8.5
>>
>> By the way I noticed another potential issue, If I hard code java path to
>> a jdk7 but don't set JAVA_HOME to it, then keytool runs with JDK6 (because
>> it's the one in the path), should we check this ?
>>
>> Logs:
>> 2013/10/04 04:41:14 WARN - jmeter.protocol.http.proxy.ProxyControl:
>> Could not open/read key store
>> /data/decathlon/workspace/jmeter/bin/proxyserver.jks (No such file or
>> directory)
>> 2013/10/04 04:41:14 INFO - jmeter.protocol.http.proxy.ProxyControl:
>> Creating Proxy CA in /data/decathlon/workspace/jmeter/bin/proxyserver.jks
>> 2013/10/04 04:41:17 INFO - jmeter.protocol.http.proxy.ProxyControl:
>> Created keystore in /data/decathlon/workspace/jmeter/bin/proxyserver.jks
>> 2013/10/04 04:41:17 INFO - jmeter.protocol.http.proxy.ProxyControl:
>> Creating entry github.global.ssl.fastly.net in
>> /data/decathlon/workspace/jmeter/bin/proxyserver.jks
>> 2013/10/04 04:41:19 INFO - jmeter.protocol.http.proxy.ProxyControl:
>> Creating entry github.com in
>> /data/decathlon/workspace/jmeter/bin/proxyserver.jks
>> 2013/10/04 04:41:21 INFO - jmeter.protocol.http.proxy.Daemon: Creating
>> Daemon Socket on port: 8888
>> 2013/10/04 04:41:21 INFO - jmeter.protocol.http.proxy.Daemon: Proxy up
>> and running!
>> 2013/10/04 04:41:33 INFO - jmeter.protocol.http.proxy.ProxyControl:
>> [53076] Creating entry www.google.com in
>> /data/decathlon/workspace/jmeter/bin/proxyserver.jks
>> 2013/10/04 04:41:36 WARN - jmeter.protocol.http.proxy.Proxy: [53076]
>> Problem with SSL certificate for 'www.google.com'? Ensure browser is set
>> to accept the JMeter proxy cert: Received fatal alert: unknown_ca
>> 2013/10/04 04:41:43 WARN - jmeter.protocol.http.proxy.Proxy: [53077]
>> Problem with SSL certificate for 'github.com'? Ensure browser is set to
>> accept the JMeter proxy cert: Received fatal alert: unknown_ca
>> 2013/10/04 04:41:47 WARN - jmeter.protocol.http.proxy.Proxy: [53078]
>> Problem with SSL certificate for 'github.com'? Ensure browser is set to
>> accept the JMeter proxy cert: Received fatal alert: unknown_ca
>> 2013/10/04 04:41:50 WARN - jmeter.protocol.http.proxy.Proxy: [53082]
>> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>> unknown_ca
>> 2013/10/04 04:41:50 WARN - jmeter.protocol.http.proxy.Proxy: [53088]
>> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>> unknown_ca
>> 2013/10/04 04:41:50 WARN - jmeter.protocol.http.proxy.Proxy: [53086]
>> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>> unknown_ca
>> 2013/10/04 04:41:50 WARN - jmeter.protocol.http.proxy.Proxy: [53087]
>> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>> unknown_ca
>> 2013/10/04 04:44:37 WARN - jmeter.protocol.http.proxy.Proxy: [53108]
>> Problem with SSL certificate for 'github.com'? Ensure browser is set to
>> accept the JMeter proxy cert: Received fatal alert: unknown_ca
>> 2013/10/04 04:44:42 WARN - jmeter.protocol.http.proxy.Proxy: [53109]
>> Problem with SSL certificate for 'github.com'? Ensure browser is set to
>> accept the JMeter proxy cert: Received fatal alert: unknown_ca
>> 2013/10/04 04:44:45 WARN - jmeter.protocol.http.proxy.Proxy: [53112]
>> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>> unknown_ca
>> 2013/10/04 04:44:45 WARN - jmeter.protocol.http.proxy.Proxy: [53114]
>> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>> unknown_ca
>> 2013/10/04 04:44:45 WARN - jmeter.protocol.http.proxy.Proxy: [53116]
>> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>> unknown_ca
>> 2013/10/04 04:44:45 WARN - jmeter.protocol.http.proxy.Proxy: [53115]
>> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>> unknown_ca
>> 2013/10/04 04:44:45 WARN - jmeter.protocol.http.proxy.Proxy: [53117]
>> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>> unknown_ca
>> 2013/10/04 04:44:58 WARN - jmeter.protocol.http.proxy.Proxy: [53132]
>> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>> unknown_ca
>> 2013/10/04 04:44:58 WARN - jmeter.protocol.http.proxy.Proxy: [53134]
>> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>> unknown_ca
>> 2013/10/04 04:44:58 WARN - jmeter.protocol.http.proxy.Proxy: [53135]
>> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>> unknown_ca
>> 2013/10/04 04:44:58 WARN - jmeter.protocol.http.proxy.Proxy: [53136]
>> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>> unknown_ca
>> 2013/10/04 04:45:11 WARN - jmeter.protocol.http.proxy.Proxy: [53148]
>> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>> unknown_ca
>> 2013/10/04 04:45:15 WARN - jmeter.protocol.http.proxy.Proxy: [53149]
>> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>> unknown_ca
>> 2013/10/04 04:45:27 WARN - jmeter.protocol.http.proxy.Proxy: [53165]
>> Problem with SSL certificate for 'ssl.google-analytics.com'? Ensure
>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>> unknown_ca
>> 2013/10/04 04:45:28 WARN - jmeter.protocol.http.proxy.Proxy: [53160]
>> Empty request, ignored
>> 2013/10/04 04:45:29 WARN - jmeter.protocol.http.proxy.Proxy: [53167]
>> Problem with SSL certificate for 'collector.githubapp.com'? Ensure
>> browser is set to accept the JMeter proxy cert: Received fatal alert:
>> unknown_ca
>>
>>
>> Regards
>> Philippe
>>
>>
>>
>>
>> On Thu, Oct 3, 2013 at 7:05 PM, sebb <se...@gmail.com> wrote:
>>
>>> On 3 October 2013 14:28, Philippe Mouawad <ph...@gmail.com>
>>> wrote:
>>> > Hello sebb,
>>> > You can do the test just call https://github.com
>>>
>>> I had some problems initially, but after removing proxyserver.jks it
>>> all seems to work OK.
>>>
>>> I've updated the code with better logging; also the validity of the
>>> root CA is now checked.
>>>
>>> Please try again.
>>>
>>> > Regards
>>> > Philippe
>>> >
>>> >
>>> > On Thu, Oct 3, 2013 at 2:45 PM, sebb <se...@gmail.com> wrote:
>>> >
>>> >> On 1 October 2013 22:14, Philippe Mouawad <philippe.mouawad@gmail.com
>>> >
>>> >> wrote:
>>> >> > Hello,
>>> >> > Testing new Proxy recording on github, I finally managed to record
>>> but
>>> >> this
>>> >> > time it was not as easy as for other websites:
>>> >> >
>>> >> > I finally succeeded by calling in browser:
>>> >> > - https://ssl.fastly.net and accepting jmeter certificate
>>> >> > - collector.githubapp.com and accepting jmeter certificate
>>> >> >
>>> >> > Just adding this in HTTPS Domain was not enough:
>>> >> > github.global.ssl.fastly.net,*.github.com,
>>> github.global.ssl.fastly.net,
>>> >> > collector.githubapp.com,ssl.google-analytics.com
>>> >>
>>> >> Why not use domains for them all?
>>> >>
>>> >> *.fastly.net
>>> >> *.github.com
>>> >> *.githubapp.com
>>> >> *.google-analytics.com
>>> >>
>>> >> > Is this what was expected ?
>>> >> > I would have thought accepting JMeter CA would be enough
>>> >> >
>>> >> > Am I missing something ?
>>> >>
>>> >> Presumably.
>>> >>
>>> >> What URLs did you visit?
>>> >>
>>> >> What does the jmeter log say?
>>> >> It should report warnings for missing certificates; if no extra logs
>>> >> or changed levels may be needed.
>>> >>
>>> >> > By the way, before release we need to finish this:
>>> >> > - Document the changes made on JMeter Proxy Server
>>> >> > - Rename it
>>> >> > - Update screenshots for changes and maybe reference documentation
>>> >> >
>>> >> > Regards
>>> >> > Philippe
>>> >>
>>> >
>>> >
>>> >
>>> > --
>>> > Cordialement.
>>> > Philippe Mouawad.
>>>
>>
>>
>>
>> --
>> Cordialement.
>> Philippe Mouawad.
>>
>>
>>
>
>
> --
> Cordialement.
> Philippe Mouawad.
>
>
>
--
Cordialement.
Philippe Mouawad.
Re: JMeter nightly build and recording
Posted by Philippe Mouawad <ph...@gmail.com>.
Hello sebb,
Do I need to open the ApacheJMeterTemporaryRootCA.crt in Firefox and accept
it as authority for Websites so that it works ?
If yes then it works, but it should be documented and popup that creates
the proxyservers and shows FingerPrint of Root CA shoud say this.
If not then it is not working for me.
Regards
Philippe
On Fri, Oct 4, 2013 at 4:54 AM, Philippe Mouawad <philippe.mouawad@gmail.com
> wrote:
> Hello sebb,
> Gave it another try, still have to manually enter URL for
> github.global.ssl.fastly.net and accept certificate, same for
> collector.githubapp.com'
> I am using FF 24.0 on Mac OSX 10.6.8 or 10.8.5
>
> By the way I noticed another potential issue, If I hard code java path to
> a jdk7 but don't set JAVA_HOME to it, then keytool runs with JDK6 (because
> it's the one in the path), should we check this ?
>
> Logs:
> 2013/10/04 04:41:14 WARN - jmeter.protocol.http.proxy.ProxyControl: Could
> not open/read key store
> /data/decathlon/workspace/jmeter/bin/proxyserver.jks (No such file or
> directory)
> 2013/10/04 04:41:14 INFO - jmeter.protocol.http.proxy.ProxyControl:
> Creating Proxy CA in /data/decathlon/workspace/jmeter/bin/proxyserver.jks
> 2013/10/04 04:41:17 INFO - jmeter.protocol.http.proxy.ProxyControl:
> Created keystore in /data/decathlon/workspace/jmeter/bin/proxyserver.jks
> 2013/10/04 04:41:17 INFO - jmeter.protocol.http.proxy.ProxyControl:
> Creating entry github.global.ssl.fastly.net in
> /data/decathlon/workspace/jmeter/bin/proxyserver.jks
> 2013/10/04 04:41:19 INFO - jmeter.protocol.http.proxy.ProxyControl:
> Creating entry github.com in
> /data/decathlon/workspace/jmeter/bin/proxyserver.jks
> 2013/10/04 04:41:21 INFO - jmeter.protocol.http.proxy.Daemon: Creating
> Daemon Socket on port: 8888
> 2013/10/04 04:41:21 INFO - jmeter.protocol.http.proxy.Daemon: Proxy up
> and running!
> 2013/10/04 04:41:33 INFO - jmeter.protocol.http.proxy.ProxyControl:
> [53076] Creating entry www.google.com in
> /data/decathlon/workspace/jmeter/bin/proxyserver.jks
> 2013/10/04 04:41:36 WARN - jmeter.protocol.http.proxy.Proxy: [53076]
> Problem with SSL certificate for 'www.google.com'? Ensure browser is set
> to accept the JMeter proxy cert: Received fatal alert: unknown_ca
> 2013/10/04 04:41:43 WARN - jmeter.protocol.http.proxy.Proxy: [53077]
> Problem with SSL certificate for 'github.com'? Ensure browser is set to
> accept the JMeter proxy cert: Received fatal alert: unknown_ca
> 2013/10/04 04:41:47 WARN - jmeter.protocol.http.proxy.Proxy: [53078]
> Problem with SSL certificate for 'github.com'? Ensure browser is set to
> accept the JMeter proxy cert: Received fatal alert: unknown_ca
> 2013/10/04 04:41:50 WARN - jmeter.protocol.http.proxy.Proxy: [53082]
> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
> browser is set to accept the JMeter proxy cert: Received fatal alert:
> unknown_ca
> 2013/10/04 04:41:50 WARN - jmeter.protocol.http.proxy.Proxy: [53088]
> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
> browser is set to accept the JMeter proxy cert: Received fatal alert:
> unknown_ca
> 2013/10/04 04:41:50 WARN - jmeter.protocol.http.proxy.Proxy: [53086]
> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
> browser is set to accept the JMeter proxy cert: Received fatal alert:
> unknown_ca
> 2013/10/04 04:41:50 WARN - jmeter.protocol.http.proxy.Proxy: [53087]
> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
> browser is set to accept the JMeter proxy cert: Received fatal alert:
> unknown_ca
> 2013/10/04 04:44:37 WARN - jmeter.protocol.http.proxy.Proxy: [53108]
> Problem with SSL certificate for 'github.com'? Ensure browser is set to
> accept the JMeter proxy cert: Received fatal alert: unknown_ca
> 2013/10/04 04:44:42 WARN - jmeter.protocol.http.proxy.Proxy: [53109]
> Problem with SSL certificate for 'github.com'? Ensure browser is set to
> accept the JMeter proxy cert: Received fatal alert: unknown_ca
> 2013/10/04 04:44:45 WARN - jmeter.protocol.http.proxy.Proxy: [53112]
> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
> browser is set to accept the JMeter proxy cert: Received fatal alert:
> unknown_ca
> 2013/10/04 04:44:45 WARN - jmeter.protocol.http.proxy.Proxy: [53114]
> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
> browser is set to accept the JMeter proxy cert: Received fatal alert:
> unknown_ca
> 2013/10/04 04:44:45 WARN - jmeter.protocol.http.proxy.Proxy: [53116]
> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
> browser is set to accept the JMeter proxy cert: Received fatal alert:
> unknown_ca
> 2013/10/04 04:44:45 WARN - jmeter.protocol.http.proxy.Proxy: [53115]
> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
> browser is set to accept the JMeter proxy cert: Received fatal alert:
> unknown_ca
> 2013/10/04 04:44:45 WARN - jmeter.protocol.http.proxy.Proxy: [53117]
> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
> browser is set to accept the JMeter proxy cert: Received fatal alert:
> unknown_ca
> 2013/10/04 04:44:58 WARN - jmeter.protocol.http.proxy.Proxy: [53132]
> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
> browser is set to accept the JMeter proxy cert: Received fatal alert:
> unknown_ca
> 2013/10/04 04:44:58 WARN - jmeter.protocol.http.proxy.Proxy: [53134]
> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
> browser is set to accept the JMeter proxy cert: Received fatal alert:
> unknown_ca
> 2013/10/04 04:44:58 WARN - jmeter.protocol.http.proxy.Proxy: [53135]
> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
> browser is set to accept the JMeter proxy cert: Received fatal alert:
> unknown_ca
> 2013/10/04 04:44:58 WARN - jmeter.protocol.http.proxy.Proxy: [53136]
> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
> browser is set to accept the JMeter proxy cert: Received fatal alert:
> unknown_ca
> 2013/10/04 04:45:11 WARN - jmeter.protocol.http.proxy.Proxy: [53148]
> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
> browser is set to accept the JMeter proxy cert: Received fatal alert:
> unknown_ca
> 2013/10/04 04:45:15 WARN - jmeter.protocol.http.proxy.Proxy: [53149]
> Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
> browser is set to accept the JMeter proxy cert: Received fatal alert:
> unknown_ca
> 2013/10/04 04:45:27 WARN - jmeter.protocol.http.proxy.Proxy: [53165]
> Problem with SSL certificate for 'ssl.google-analytics.com'? Ensure
> browser is set to accept the JMeter proxy cert: Received fatal alert:
> unknown_ca
> 2013/10/04 04:45:28 WARN - jmeter.protocol.http.proxy.Proxy: [53160]
> Empty request, ignored
> 2013/10/04 04:45:29 WARN - jmeter.protocol.http.proxy.Proxy: [53167]
> Problem with SSL certificate for 'collector.githubapp.com'? Ensure
> browser is set to accept the JMeter proxy cert: Received fatal alert:
> unknown_ca
>
>
> Regards
> Philippe
>
>
>
>
> On Thu, Oct 3, 2013 at 7:05 PM, sebb <se...@gmail.com> wrote:
>
>> On 3 October 2013 14:28, Philippe Mouawad <ph...@gmail.com>
>> wrote:
>> > Hello sebb,
>> > You can do the test just call https://github.com
>>
>> I had some problems initially, but after removing proxyserver.jks it
>> all seems to work OK.
>>
>> I've updated the code with better logging; also the validity of the
>> root CA is now checked.
>>
>> Please try again.
>>
>> > Regards
>> > Philippe
>> >
>> >
>> > On Thu, Oct 3, 2013 at 2:45 PM, sebb <se...@gmail.com> wrote:
>> >
>> >> On 1 October 2013 22:14, Philippe Mouawad <ph...@gmail.com>
>> >> wrote:
>> >> > Hello,
>> >> > Testing new Proxy recording on github, I finally managed to record
>> but
>> >> this
>> >> > time it was not as easy as for other websites:
>> >> >
>> >> > I finally succeeded by calling in browser:
>> >> > - https://ssl.fastly.net and accepting jmeter certificate
>> >> > - collector.githubapp.com and accepting jmeter certificate
>> >> >
>> >> > Just adding this in HTTPS Domain was not enough:
>> >> > github.global.ssl.fastly.net,*.github.com,
>> github.global.ssl.fastly.net,
>> >> > collector.githubapp.com,ssl.google-analytics.com
>> >>
>> >> Why not use domains for them all?
>> >>
>> >> *.fastly.net
>> >> *.github.com
>> >> *.githubapp.com
>> >> *.google-analytics.com
>> >>
>> >> > Is this what was expected ?
>> >> > I would have thought accepting JMeter CA would be enough
>> >> >
>> >> > Am I missing something ?
>> >>
>> >> Presumably.
>> >>
>> >> What URLs did you visit?
>> >>
>> >> What does the jmeter log say?
>> >> It should report warnings for missing certificates; if no extra logs
>> >> or changed levels may be needed.
>> >>
>> >> > By the way, before release we need to finish this:
>> >> > - Document the changes made on JMeter Proxy Server
>> >> > - Rename it
>> >> > - Update screenshots for changes and maybe reference documentation
>> >> >
>> >> > Regards
>> >> > Philippe
>> >>
>> >
>> >
>> >
>> > --
>> > Cordialement.
>> > Philippe Mouawad.
>>
>
>
>
> --
> Cordialement.
> Philippe Mouawad.
>
>
>
--
Cordialement.
Philippe Mouawad.
Re: JMeter nightly build and recording
Posted by sebb <se...@gmail.com>.
On 4 October 2013 03:54, Philippe Mouawad <ph...@gmail.com> wrote:
> Hello sebb,
> Gave it another try, still have to manually enter URL for
> github.global.ssl.fastly.net and accept certificate, same for
> collector.githubapp.com'
> I am using FF 24.0 on Mac OSX 10.6.8 or 10.8.5
>
> By the way I noticed another potential issue, If I hard code java path to a
> jdk7 but don't set JAVA_HOME to it, then keytool runs with JDK6 (because
> it's the one in the path), should we check this ?
>
If it's easy to do so, but not worth spending much time on as it's
effectively a broken Java installation.
Re: JMeter nightly build and recording
Posted by Philippe Mouawad <ph...@gmail.com>.
Hello sebb,
Gave it another try, still have to manually enter URL for
github.global.ssl.fastly.net and accept certificate, same for
collector.githubapp.com'
I am using FF 24.0 on Mac OSX 10.6.8 or 10.8.5
By the way I noticed another potential issue, If I hard code java path to a
jdk7 but don't set JAVA_HOME to it, then keytool runs with JDK6 (because
it's the one in the path), should we check this ?
Logs:
2013/10/04 04:41:14 WARN - jmeter.protocol.http.proxy.ProxyControl: Could
not open/read key store
/data/decathlon/workspace/jmeter/bin/proxyserver.jks (No such file or
directory)
2013/10/04 04:41:14 INFO - jmeter.protocol.http.proxy.ProxyControl:
Creating Proxy CA in /data/decathlon/workspace/jmeter/bin/proxyserver.jks
2013/10/04 04:41:17 INFO - jmeter.protocol.http.proxy.ProxyControl:
Created keystore in /data/decathlon/workspace/jmeter/bin/proxyserver.jks
2013/10/04 04:41:17 INFO - jmeter.protocol.http.proxy.ProxyControl:
Creating entry github.global.ssl.fastly.net in
/data/decathlon/workspace/jmeter/bin/proxyserver.jks
2013/10/04 04:41:19 INFO - jmeter.protocol.http.proxy.ProxyControl:
Creating entry github.com in
/data/decathlon/workspace/jmeter/bin/proxyserver.jks
2013/10/04 04:41:21 INFO - jmeter.protocol.http.proxy.Daemon: Creating
Daemon Socket on port: 8888
2013/10/04 04:41:21 INFO - jmeter.protocol.http.proxy.Daemon: Proxy up and
running!
2013/10/04 04:41:33 INFO - jmeter.protocol.http.proxy.ProxyControl:
[53076] Creating entry www.google.com in
/data/decathlon/workspace/jmeter/bin/proxyserver.jks
2013/10/04 04:41:36 WARN - jmeter.protocol.http.proxy.Proxy: [53076]
Problem with SSL certificate for 'www.google.com'? Ensure browser is set to
accept the JMeter proxy cert: Received fatal alert: unknown_ca
2013/10/04 04:41:43 WARN - jmeter.protocol.http.proxy.Proxy: [53077]
Problem with SSL certificate for 'github.com'? Ensure browser is set to
accept the JMeter proxy cert: Received fatal alert: unknown_ca
2013/10/04 04:41:47 WARN - jmeter.protocol.http.proxy.Proxy: [53078]
Problem with SSL certificate for 'github.com'? Ensure browser is set to
accept the JMeter proxy cert: Received fatal alert: unknown_ca
2013/10/04 04:41:50 WARN - jmeter.protocol.http.proxy.Proxy: [53082]
Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
browser is set to accept the JMeter proxy cert: Received fatal alert:
unknown_ca
2013/10/04 04:41:50 WARN - jmeter.protocol.http.proxy.Proxy: [53088]
Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
browser is set to accept the JMeter proxy cert: Received fatal alert:
unknown_ca
2013/10/04 04:41:50 WARN - jmeter.protocol.http.proxy.Proxy: [53086]
Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
browser is set to accept the JMeter proxy cert: Received fatal alert:
unknown_ca
2013/10/04 04:41:50 WARN - jmeter.protocol.http.proxy.Proxy: [53087]
Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
browser is set to accept the JMeter proxy cert: Received fatal alert:
unknown_ca
2013/10/04 04:44:37 WARN - jmeter.protocol.http.proxy.Proxy: [53108]
Problem with SSL certificate for 'github.com'? Ensure browser is set to
accept the JMeter proxy cert: Received fatal alert: unknown_ca
2013/10/04 04:44:42 WARN - jmeter.protocol.http.proxy.Proxy: [53109]
Problem with SSL certificate for 'github.com'? Ensure browser is set to
accept the JMeter proxy cert: Received fatal alert: unknown_ca
2013/10/04 04:44:45 WARN - jmeter.protocol.http.proxy.Proxy: [53112]
Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
browser is set to accept the JMeter proxy cert: Received fatal alert:
unknown_ca
2013/10/04 04:44:45 WARN - jmeter.protocol.http.proxy.Proxy: [53114]
Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
browser is set to accept the JMeter proxy cert: Received fatal alert:
unknown_ca
2013/10/04 04:44:45 WARN - jmeter.protocol.http.proxy.Proxy: [53116]
Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
browser is set to accept the JMeter proxy cert: Received fatal alert:
unknown_ca
2013/10/04 04:44:45 WARN - jmeter.protocol.http.proxy.Proxy: [53115]
Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
browser is set to accept the JMeter proxy cert: Received fatal alert:
unknown_ca
2013/10/04 04:44:45 WARN - jmeter.protocol.http.proxy.Proxy: [53117]
Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
browser is set to accept the JMeter proxy cert: Received fatal alert:
unknown_ca
2013/10/04 04:44:58 WARN - jmeter.protocol.http.proxy.Proxy: [53132]
Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
browser is set to accept the JMeter proxy cert: Received fatal alert:
unknown_ca
2013/10/04 04:44:58 WARN - jmeter.protocol.http.proxy.Proxy: [53134]
Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
browser is set to accept the JMeter proxy cert: Received fatal alert:
unknown_ca
2013/10/04 04:44:58 WARN - jmeter.protocol.http.proxy.Proxy: [53135]
Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
browser is set to accept the JMeter proxy cert: Received fatal alert:
unknown_ca
2013/10/04 04:44:58 WARN - jmeter.protocol.http.proxy.Proxy: [53136]
Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
browser is set to accept the JMeter proxy cert: Received fatal alert:
unknown_ca
2013/10/04 04:45:11 WARN - jmeter.protocol.http.proxy.Proxy: [53148]
Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
browser is set to accept the JMeter proxy cert: Received fatal alert:
unknown_ca
2013/10/04 04:45:15 WARN - jmeter.protocol.http.proxy.Proxy: [53149]
Problem with SSL certificate for 'github.global.ssl.fastly.net'? Ensure
browser is set to accept the JMeter proxy cert: Received fatal alert:
unknown_ca
2013/10/04 04:45:27 WARN - jmeter.protocol.http.proxy.Proxy: [53165]
Problem with SSL certificate for 'ssl.google-analytics.com'? Ensure browser
is set to accept the JMeter proxy cert: Received fatal alert: unknown_ca
2013/10/04 04:45:28 WARN - jmeter.protocol.http.proxy.Proxy: [53160] Empty
request, ignored
2013/10/04 04:45:29 WARN - jmeter.protocol.http.proxy.Proxy: [53167]
Problem with SSL certificate for 'collector.githubapp.com'? Ensure browser
is set to accept the JMeter proxy cert: Received fatal alert: unknown_ca
Regards
Philippe
On Thu, Oct 3, 2013 at 7:05 PM, sebb <se...@gmail.com> wrote:
> On 3 October 2013 14:28, Philippe Mouawad <ph...@gmail.com>
> wrote:
> > Hello sebb,
> > You can do the test just call https://github.com
>
> I had some problems initially, but after removing proxyserver.jks it
> all seems to work OK.
>
> I've updated the code with better logging; also the validity of the
> root CA is now checked.
>
> Please try again.
>
> > Regards
> > Philippe
> >
> >
> > On Thu, Oct 3, 2013 at 2:45 PM, sebb <se...@gmail.com> wrote:
> >
> >> On 1 October 2013 22:14, Philippe Mouawad <ph...@gmail.com>
> >> wrote:
> >> > Hello,
> >> > Testing new Proxy recording on github, I finally managed to record but
> >> this
> >> > time it was not as easy as for other websites:
> >> >
> >> > I finally succeeded by calling in browser:
> >> > - https://ssl.fastly.net and accepting jmeter certificate
> >> > - collector.githubapp.com and accepting jmeter certificate
> >> >
> >> > Just adding this in HTTPS Domain was not enough:
> >> > github.global.ssl.fastly.net,*.github.com,
> github.global.ssl.fastly.net,
> >> > collector.githubapp.com,ssl.google-analytics.com
> >>
> >> Why not use domains for them all?
> >>
> >> *.fastly.net
> >> *.github.com
> >> *.githubapp.com
> >> *.google-analytics.com
> >>
> >> > Is this what was expected ?
> >> > I would have thought accepting JMeter CA would be enough
> >> >
> >> > Am I missing something ?
> >>
> >> Presumably.
> >>
> >> What URLs did you visit?
> >>
> >> What does the jmeter log say?
> >> It should report warnings for missing certificates; if no extra logs
> >> or changed levels may be needed.
> >>
> >> > By the way, before release we need to finish this:
> >> > - Document the changes made on JMeter Proxy Server
> >> > - Rename it
> >> > - Update screenshots for changes and maybe reference documentation
> >> >
> >> > Regards
> >> > Philippe
> >>
> >
> >
> >
> > --
> > Cordialement.
> > Philippe Mouawad.
>
--
Cordialement.
Philippe Mouawad.
Re: JMeter nightly build and recording
Posted by sebb <se...@gmail.com>.
On 3 October 2013 14:28, Philippe Mouawad <ph...@gmail.com> wrote:
> Hello sebb,
> You can do the test just call https://github.com
I had some problems initially, but after removing proxyserver.jks it
all seems to work OK.
I've updated the code with better logging; also the validity of the
root CA is now checked.
Please try again.
> Regards
> Philippe
>
>
> On Thu, Oct 3, 2013 at 2:45 PM, sebb <se...@gmail.com> wrote:
>
>> On 1 October 2013 22:14, Philippe Mouawad <ph...@gmail.com>
>> wrote:
>> > Hello,
>> > Testing new Proxy recording on github, I finally managed to record but
>> this
>> > time it was not as easy as for other websites:
>> >
>> > I finally succeeded by calling in browser:
>> > - https://ssl.fastly.net and accepting jmeter certificate
>> > - collector.githubapp.com and accepting jmeter certificate
>> >
>> > Just adding this in HTTPS Domain was not enough:
>> > github.global.ssl.fastly.net,*.github.com,github.global.ssl.fastly.net,
>> > collector.githubapp.com,ssl.google-analytics.com
>>
>> Why not use domains for them all?
>>
>> *.fastly.net
>> *.github.com
>> *.githubapp.com
>> *.google-analytics.com
>>
>> > Is this what was expected ?
>> > I would have thought accepting JMeter CA would be enough
>> >
>> > Am I missing something ?
>>
>> Presumably.
>>
>> What URLs did you visit?
>>
>> What does the jmeter log say?
>> It should report warnings for missing certificates; if no extra logs
>> or changed levels may be needed.
>>
>> > By the way, before release we need to finish this:
>> > - Document the changes made on JMeter Proxy Server
>> > - Rename it
>> > - Update screenshots for changes and maybe reference documentation
>> >
>> > Regards
>> > Philippe
>>
>
>
>
> --
> Cordialement.
> Philippe Mouawad.
Re: JMeter nightly build and recording
Posted by Philippe Mouawad <ph...@gmail.com>.
Hello sebb,
You can do the test just call https://github.com
Regards
Philippe
On Thu, Oct 3, 2013 at 2:45 PM, sebb <se...@gmail.com> wrote:
> On 1 October 2013 22:14, Philippe Mouawad <ph...@gmail.com>
> wrote:
> > Hello,
> > Testing new Proxy recording on github, I finally managed to record but
> this
> > time it was not as easy as for other websites:
> >
> > I finally succeeded by calling in browser:
> > - https://ssl.fastly.net and accepting jmeter certificate
> > - collector.githubapp.com and accepting jmeter certificate
> >
> > Just adding this in HTTPS Domain was not enough:
> > github.global.ssl.fastly.net,*.github.com,github.global.ssl.fastly.net,
> > collector.githubapp.com,ssl.google-analytics.com
>
> Why not use domains for them all?
>
> *.fastly.net
> *.github.com
> *.githubapp.com
> *.google-analytics.com
>
> > Is this what was expected ?
> > I would have thought accepting JMeter CA would be enough
> >
> > Am I missing something ?
>
> Presumably.
>
> What URLs did you visit?
>
> What does the jmeter log say?
> It should report warnings for missing certificates; if no extra logs
> or changed levels may be needed.
>
> > By the way, before release we need to finish this:
> > - Document the changes made on JMeter Proxy Server
> > - Rename it
> > - Update screenshots for changes and maybe reference documentation
> >
> > Regards
> > Philippe
>
--
Cordialement.
Philippe Mouawad.
Re: JMeter nightly build and recording
Posted by sebb <se...@gmail.com>.
On 1 October 2013 22:14, Philippe Mouawad <ph...@gmail.com> wrote:
> Hello,
> Testing new Proxy recording on github, I finally managed to record but this
> time it was not as easy as for other websites:
>
> I finally succeeded by calling in browser:
> - https://ssl.fastly.net and accepting jmeter certificate
> - collector.githubapp.com and accepting jmeter certificate
>
> Just adding this in HTTPS Domain was not enough:
> github.global.ssl.fastly.net,*.github.com,github.global.ssl.fastly.net,
> collector.githubapp.com,ssl.google-analytics.com
Why not use domains for them all?
*.fastly.net
*.github.com
*.githubapp.com
*.google-analytics.com
> Is this what was expected ?
> I would have thought accepting JMeter CA would be enough
>
> Am I missing something ?
Presumably.
What URLs did you visit?
What does the jmeter log say?
It should report warnings for missing certificates; if no extra logs
or changed levels may be needed.
> By the way, before release we need to finish this:
> - Document the changes made on JMeter Proxy Server
> - Rename it
> - Update screenshots for changes and maybe reference documentation
>
> Regards
> Philippe