ViewState, Firewalls, and MaxPageStateFieldLength

Hi There,

A very small number of the users on our web sites (using .NET 1.1 or .NET
2.0) complain that the sites hang for them when they click buttons/links
that trigger postbacks. Some of these buttons are LinkButtons, some are
ImageButtons, some use Javascript, some do not. They are all unusable.

When i first heard about this i created some basic tests on our site to
check that HTTP POSTs were working in general for these users and they are.
In fact basic Web Forms outside of the context of our normal pages work
fine. Both LinkButtons and ImageButtons trigger successful postbacks
without hanging.

One of the main things that distinguishes these pages is the size of the
ViewState. The postbacks that worked had very small ViewState - approx. 50
characters. Our homepage on the other hand ViewState accounts for 20K of
the 80K file size.

I hear some firewalls can block HTTP POSTs with large ViewState so i have
cut down the size of our ViewState and also used the
MaxPageStateFieldLength setting in web.config.

Has anyone out there had Firewall issues with ViewState? Is there any
bullet proof way of ensuring firewalls don't block it short of not using it?

Also does anyone else have experience of using MaxPageStateFieldLength? It
seems to have the unfortunate side effect for us of producing a small but
steady trickle of ViewState errors with error messages like "Invalid
viewstate: Missing field: __VIEWSTATE589.".

Any help appreciated,

Nick

===================================
This list is hosted by DevelopMentor®  http://www.develop.com

View archives and manage your subscription(s) at http://discuss.develop.com