...
For extracting out hidden form fields, I used a simpler regular expression than the one in the article:
id="__+PREVIOUSPAGE"\s*value="(.*?)". For pages that had 'jammed-in' pipe-delimited data, I use this type of regular expression instead: |+PREVIOUSPAGE|(.*?)|
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. For pages that had 'jammed-in' pipe-delimited data, I use this type of regular expression instead:
|__PREVIOUSPAGE|(.*?)|
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.