>>No
>
>Well, I do not see any reference between that link and the topic of this thread. The issue here is with requestPathInvalidCharacters. The link I gave is the one that negotiates with it. Basically, it only allows us to put the equivalent of the Web.Config file in the code instead. But, in that link you gave, this is referencing something else.

Again, No.
As I read it, if you specfy you own class derived from System.Web.Util.RequestValidator then you replace the default behaviour (which checks the RequestPathInvalidCharacters property) - although you could still call the base.IsValidRequestString() if it was useful.

FWIW, unless you are yourself creating a request which would violate the default rules I'd leave well alone. If you *are* generating a genuine request that falls foul of the default then use the override to identify and allow it - otherwise just pass the validation operation to the base class.....