It should work if you redirect stderr to stdout so 2>&1 Ivan
On Tue, Jul 2, 2019 at 2:53 PM <[email protected]> wrote: > Hi, > > If the output of "openssl ocsp" is going to STDERR, then dos that mean > that there is no way to get the Response Assertion to work? > > Jim > > > On Tuesday, July 2, 2019, 8:34:46 AM EDT, Ivan Rancati < > [email protected]> wrote: > > 1. > If you try it, you will probably need to set a few headers, such as > --header='Content-Type:application/ocsp-request' > > 2. > Assuming you are testing on linux. I vaguely remember, but have not time to > try now, the output of "openssl ocsp ..." is sent to stderr and not stdout. > Maybe you can try from bash, redirecting to a file, and seeing what's in > the file > > > > > On Tue, Jul 2, 2019 at 2:16 PM <[email protected]> wrote: > > > Hi, > > > > Re. 1: That is an interesting approach! I will try it if I have some > time. > > > > Re. 2: If I use "Text Response", it looks like the Response Assertion > > doesn't even fire (doesn't appear in the results tree). So far, only > > checking "Response message" in the Response Assertion causes the Response > > Assertion to appear in results, but I still am not able to get the > > assertion to match. > > > > I have tried both "Contains" "revoked" and "substring" "revoked", but > > neither succeeds. > > > > Thanks, > > Jim > > > > > > On Tuesday, July 2, 2019, 7:46:22 AM EDT, Ivan Rancati < > > [email protected]> wrote: > > > > Two ideas > > > > 1 > > If you are testing with a limited number of certificates: > > You could manually prepare one (or more) ocsp response file with openssl, > > then use the normal HTTP Sampler to POST that request > > > > openssl ocsp -issuer <ca certificate> -cert <your certificate to be > tested> > > -reqout <the file you will POST> > > > > > > 2 > > I have a couple of test plans with OS Process Sampler and assertion. I > use > > "Text Response" in "Field to Test" > > Make sure you use "Contains" if you need a regex in "Pattern to test", I > > think "Substring" will not expand the regex > > > > best, > > Ivan > > > > > > > > > > On Tue, Jul 2, 2019 at 12:52 PM <[email protected]> wrote: > > > > > Hi, > > > > > > I couldn't get the approach that I was trying in the earlier "Help get > > > OCSP responder load test working?" thread, where I was trying to > generate > > > the OCSP request programatically, so I changed my approach. > > > > > > Now, I use an OS Process Sampler to run an "openssl ocsp" command, and > > > that seems to be working, but I would like to have an assertion > checking > > > the response message for the string "revoked". > > > > > > I tried adding a Response Assertion, but that doesn't seem to be firing > > at > > > all, even if I "attach it" to the OS Process Sampler itself. > > > > > > So is there a way to include an assertion in the Jmeter test plan that > > > would check for the string "revoked" in the response message? And, if > > so, > > > how do I do that? > > > > > > Thanks, > > > Jim > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > > >
