In which case you need to look at the HTTP requests that are arriving
at the server to see how they differ between JMeter and the browser.
The server does not know what is making the requests, so it can only
behave differently if the requests are different.
On 26 November 2015 at 09:30, rimano w
Cache manager was already added to the test plan. I followed instruction from
link provided and I still got the same results.
Just to be clear I don't have problems with JMeter/Browser cache my problem
is with cache memory on server side.
--
View this message in context:
http://jmeter.512774.n5
Hi, I cleared cache and history from browser and got the same results.
Web server still access its own cache fast.
--
View this message in context:
http://jmeter.512774.n5.nabble.com/Using-JMeter-slows-down-ASP-NET-Cache-on-IIS-tp5723495p5723501.html
Sent from the JMeter - User mailing list ar
Hi
compare the headers and responses between JMeter and browser (usually cache
control headers will not be sent by Jmeter by default) - or alternately
does your test result hold if you clear browser cache and history?
On Wed, Nov 25, 2015 at 5:49 AM, Amir Mandzuka
wrote:
> Hi.
>
> I started to u
