Am 16.07.22 um 15:56 schrieb Robin D. Wilson:
I see the same thing I saw on my test. When I tried your simplified test
with 2 requests to"https://www.google.com;... Here's my setup:
Test Plan
Cookie Manager
Thread Group
HTTP Request (https://www.google.com)
HTTP
I'm so curious that I gave it a try myself, but I don't see the reported
problem. Everything looks fine to me.
One thing though, I put the Cookie Manager within Thread Group, not outside
of it and under the Test Plan.
If trying that still won't work for you, I'm afraid that you need to post
your
On Sat, Jul 16, 2022 at 7:20 AM Felix Schumacher wrote:
> Am 16.07.22 um 00:43 schrieb Tong Sun:
>
> Hi,
>
> I'm sending my JMeter test results to InfluxDB, which is in a container in
> an Azure VM (in the cloud).
>
> During the test I observed only 5 connection timeouts in the JMeter log to
>
I see the same thing I saw on my test. When I tried your simplified test
with 2 requests to "https://www.google.com;... Here's my setup:
Test Plan
Cookie Manager
Thread Group
HTTP Request (https://www.google.com)
HTTP Request (https://www.google.com)
View Results
Hi Dave.
At the moment, there is no such assertion directly available. You can
achieve this by combining an extractor and add a validator on the
extracted data.
If you want to contribute a direct assertion, you can either go the
route of publishing a plugin for yourself:
Without seeing your test, it is a bit difficult to answer without guessing.
Guessing, I would say, the cookie has a secure flag set and you are
using http (which is not considered secure).
Try a simple test case for yourself, add a cookie manager, a view
results tree and two samplers to