svn commit: r571784 - /jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/component_reference.xml

[se...@apache.org]

Author: sebb
Date: Sat Sep  1 05:27:43 2007
New Revision: 571784

URL: http://svn.apache.org/viewvc?rev=571784&view=rev
Log:
Add note re cookies and auto redirects

Modified:
    jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/component_reference.xml

Modified: jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/component_reference.xml
URL: http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/component_reference.xml?rev=571784&r1=571783&r2=571784&view=diff
==============================================================================
--- jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/component_reference.xml (original)
+++ jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/component_reference.xml Sat Sep  1 05:27:43 2007
@@ -159,6 +159,7 @@
 		Sets the underlying http protocol handler to automatically follow redirects,
 		so they are not seen by JMeter, and thus will not appear as samples.
 		In versions after 2.2, this is now the default.
+		<b>Warning: see below for information on cookie handling.</b>
         </property>
 		<property name="Follow Redirects" required="Yes">
 		This only has any effect if "Redirect Automatically" is not enabled.
@@ -204,6 +205,16 @@
         http://server\.com/.*
         </property>
 </properties>
+<p>
+<b>N.B.</b> when using automatic redirection, cookies are only sent for the initial URL.
+This can cause unexpected behaviour for web-sites that redirect to a local server.
+E.g. if www.example.com redirects to www.example.co.uk.
+In this case the server will probably return cookies for both URLs, but JMeter will only see the cookies for the last
+host, i.e. www.example.co.uk. If the next request uses www.example.com, 
+rather than www.example.co.uk, it will not get the correct cookies.
+This is generally only a problem for manually created test plans,
+as a test plan created using a recorder would continue from the redirected URL.
+</p>
 <p>Upto and including JMeter 2.1.1, only responses with the content-type "text/html" were scanned for
 embedded resources. Other content-types were assumed to be something other than HTML.
 JMeter 2.1.2 introduces the a new property <b>HTTPResponse.parsers</b>, which is a list of parser ids,



---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org