jmeter-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From s...@apache.org
Subject svn commit: r1361559 - /jmeter/trunk/xdocs/usermanual/component_reference.xml
Date Sat, 14 Jul 2012 16:30:17 GMT
Author: sebb
Date: Sat Jul 14 16:30:17 2012
New Revision: 1361559

URL: http://svn.apache.org/viewvc?rev=1361559&view=rev
Log:
Fix up documentation
Bugzilla Id: 53522

Modified:
    jmeter/trunk/xdocs/usermanual/component_reference.xml

Modified: jmeter/trunk/xdocs/usermanual/component_reference.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/component_reference.xml?rev=1361559&r1=1361558&r2=1361559&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/component_reference.xml (original)
+++ jmeter/trunk/xdocs/usermanual/component_reference.xml Sat Jul 14 16:30:17 2012
@@ -3225,7 +3225,9 @@ and if so, the If-Last-Modified and If-N
 Additionally, if the "Use Cache-Control/Expires header" option is selected, then the Cache-Control/Expires
value is checked against the current time.
 If the request is a GET request, and the timestamp is in the future, then the sampler returns
immediately,
 without requesting the URL from the remote server. This is intended to emulate browser behaviour.
-Note that if Cache-Control header is "no-cache", response will not be stored in cache, if
Cache-Control has any other value, 
+Note that if Cache-Control header is "no-cache", the response will be stored in cache as
pre-expired,
+so will generate a conditional GET request.
+If Cache-Control has any other value, 
 the "max-age" expiry option is processed to compute entry lifetime, if missing then expire
header will be used, if also missing entry will be cached 
 as sas specified in <a href="http://www.ietf.org/rfc/rfc2616.txt">RFC 2616</a>
section 13.2.4. 
 </p>



Mime
View raw message