sebb wrote:
AFAICS, the MD5 calculated on the response data only, which does not include the HTTP headers. Or perhaps you are referring to headers in the HTML?
Tracked down the issue: I was using the fmt:dateFormat JSTL tag to output an year, but in the absence of an "Accept-Language" header this tag was generating a long date string containing everything up to the second (this can be fixed by setting a default locale in the web.xml through the javax.servlet.jsp.jstl.fmt.locale context parameter). In consequence the MD5 of the page was changing every second! Good thing I ran this test :-)
If you have Java coding expertise, you could use the BeanShell Assertion to do whatever you like.
Just thought that having the MD5Hex assertion set itself upon the first invocation would be quite convenient...
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
