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 <[email protected]> wrote: > 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.nabble.com/Using-JMeter-slows-down-ASP-NET-Cache-on-IIS-tp5723495p5723502.html > Sent from the JMeter - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
