M
Max Metral
Ok, I have a global page class derived from System.Web.UI.Page, let's call
it BasePage. I have another class derived from that called MemberPage. It
checks the Form collection if it's a post for some "common" fields.
Now, I have an aspx page whose code behind derives from BasePage, and which
sets ValidateRequest=False in the page directive of the aspx. I can post
<script> tags and such with no problems.
However, when I make the code-behind derive from MemberPage, it throws an
exception in ValidateRequest for the Form collection *EVEN THOUGH
VALIDATEREQUEST IS FALSE*.
I don't understand how this could possibly be correct behavior?
it BasePage. I have another class derived from that called MemberPage. It
checks the Form collection if it's a post for some "common" fields.
Now, I have an aspx page whose code behind derives from BasePage, and which
sets ValidateRequest=False in the page directive of the aspx. I can post
<script> tags and such with no problems.
However, when I make the code-behind derive from MemberPage, it throws an
exception in ValidateRequest for the Form collection *EVEN THOUGH
VALIDATEREQUEST IS FALSE*.
I don't understand how this could possibly be correct behavior?