On 3 October 2013 14:28, Philippe Mouawad <[email protected]> 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 <[email protected]> wrote: > >> On 1 October 2013 22:14, Philippe Mouawad <[email protected]> >> 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.
