This content has been marked as final. Show 2 replies
When you have any variables that are not being correlated as you assume they should, the quickest verification is to turn off all other correlation rules except your custom one (and/or in this case the default openscript viewstate rule). Most likely there is another rule that is matching some sub-string contained in the viewstate. Since viewstate is usually extremely long it's possible for a substring mismatch. In the end you will be able to move the most important rule to the top of the correlation rules/library list. I have not worked on a .NET application with viewstate/eventvalidation in any 9.x version, but I recall similar problems in older versions.1 person found this helpful
Thanks for that. I'd already headed down the route of re-ordering my custom correlation rules but haven't actually tried disabling the majority.