Page History

...

Response Field to check: Body
Reference Name: VIEWSTATE
Wiki MarkupRegular Expression: id="_VIEWSTATE" value="(\[\\w/-_\].+)"
Template: $1$
Match No. : 1
Default Value: NOT FOUND

Response Field to check: Body
Reference Name: EVENTVALIDATIONunmigrated-wiki-markup
Regular Expression: id="_EVENTVALIDATION" value="(\[\\w/-_\].+)"
Template: $1$
Match No. : 1
Default Value: NOT FOUND

Then in order to ensure these extracted values are passed in subsequent HTTP requests, for each request specify the following to be the Send Parameters for the Request:

Name: _VIEWSTATE
Value: ${VIEWSTATE}
Name: _EVENTVALIDATION
Value: ${EVENTVALIDATION}

...

For extracting out hidden form fields, I used a simpler regular expression than the one in the article: <br/>
id="__+PREVIOUSPAGE"\s*value="(.*?)"<br/>
(I'm reluctant to replace the one in the main article, unless I know the reason for it). Note the '?' used to specify non-greedy regular-expression matching. For pages that had 'jammed-in' pipe-delimited data, I use this type of regular expression instead: <br/>
|__|+PREVIOUSPAGE|(.*?)|<br/>

Note the '?' used to specify non-greedy regular-expression matching. I'm reluctant to replace the one in the main article, unless I know the reason for it.

I normally strip the automatically-generated 'Browser-derived headers' HTTP Header Manager element from my scripts. I found that doing so with the ASP.NET site resulted in page load errors. I can only ASP.NET assume uses the Header referrer for some strange reason. So, you may have to keep the 'Browser-derived headers' in.