https://bz.apache.org/bugzilla/show_bug.cgi?id=64915
Bug ID: 64915
Summary: JMeter Cache Manager misbehaving when "Use
Cache-Control/Expires header" is checked
Product: JMeter
Version: 5.2.1
Hardware: PC
OS: Mac OS X 10.1
Status: NEW
Severity: normal
Priority: P2
Component: HTTP
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: JMETER_5.4
Finding that for normal GET requests (REST API transactions) which don't return
any of the relevant cache-control/expires (or Last-Modified) headers, Jmeter
seems to cache the request and use it on subsequent transactions.
The headers returned with the JSON are:
HTTP/1.1 200
Content-Type: application/json;charset=UTF-8
Content-Length: 1321
Date: Tue, 10 Nov 2020 22:03:36 GMT
Vary: Accept-Encoding
Content-Encoding: gzip
Connection: keep-alive
Both Firefox and Chrome will go ahead and send the GET transaction to the
server, but with JMeter the 2nd and subsequent transaction with the same path
is not fired (it does pass control to the pre-processor).
This bug does not reproduce with JMeter 3.2 but does with 5.2.1 and 5.3
--
You are receiving this mail because:
You are the assignee for the bug.
