Looking into RFC 2616 <http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html> I believe that it'll be quite enough to add a HTTP Cache Manager <http://blazemeter.com/blog/using-http-cache-manager> to resolve the issue you're facing.
-- View this message in context: http://jmeter.512774.n5.nabble.com/why-getting-304-Response-code-in-sampler-result-tp5722017p5722038.html Sent from the JMeter - Dev mailing list archive at Nabble.com.
