Depends on whether you are trying to emulate what a browser does or give the server indigestion by serving up stale tokens ;-)
Seriously. If you want to test how the server responds to normal (i.e. browser) requests, then process the token as a browser would, which presumably means it will only keep it as long as it is in the form. [I'm assuming these tokens are not cookies]. If you want to check that the server really does reject stale or invalid tokens, then keep them around and/or invent them and see what happens. Browsers maintain very little state between sessions: * cookies (except session cookies) * cached pages (perhaps) so make sure JMeter does the same if you want to emulate what the browser does. [Yes, I know JMeter does not cache pages yet. Treat it like a browser with caching turned off.] S. On 03/07/07, aidy lewis <[EMAIL PROTECTED]> wrote:
Hi, The problem is with the struts token. Is it a good idea to delete their values. Or should I attempt to capture and re-use the value? Aidy --------------------------------------------------------------------- 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]
