ASP.NET Presentation Validation - ASP.NET 1.1 versus ASP.NET 3.5

we are in the process of migrating our web application from ASP.NET 1.1 to ASP.NET 3.5. Our application runs on multiple servers through DNS round robin, so each browser request may end up on a different server. We have it in our web.config to prevent validation errors.

However, our plan was to migrate one server at a time. Now it looks like when the user loads the page at 1.1. server and then page ends on server 3.5 after postback, no view state check is done.

I haven't been able to find anything on the internet regarding this issue - I'm just assuming the view state check is incompatible between 1.1. and 3.5, that is, a view item generated by 1.1 will not check for 3.5 even with the same machine key and vice versa.

Can anyone confirm this suspicion?

thank

+1


source to share


3 answers


Use sticky sessions as mentioned in this similar post . This will keep users on the same machine for a certain period of time.



I don't think it would be wise to let one user hit three different versions of the framework in a single session.

+1


source


Are you using IIS7 for host 3.5? I ran into a lot of problems when ViewState was running App 1.1 on IIS7. Running Application 1.1 correctly on IIS7 is quite tricky, not to mention trying to web garden in multiple versions of the framework. The biggest thing I have come across is that the ViewState is encrypted or managed differently than the previous version of IIS. If you try to set weg-garden to 1.1 you will get all sorts of ViewState encryption errors. You cannot set up a web garden (have multiple worker threads) in application 1.1 on IIS7. At least in my experience.



0


source


I believe 1.1 and 2.0 use different default ciphers for the viewstate. The default for 1.1 was 3DES, and I believe it was SHA1 for 2.0 (although I can't find any documentation to support this at the moment). Try setting validation in your machine key to 3DES on the new server and see if that solves the problem.

<machineKey validation="3DES">

      

0


source







All Articles