«

Hello,

In one of our VB.Net 2003 apps, we're receiving the following error:
A potentially dangerous Request.QueryString value was detected from the
client (id="RKVW8oNcLoE=").

At first glance I assumed the '=' was the problem, but when we use
'id=VQmAq6M5E/I=' in the same URL it works just fine. Any suggestions? I
know I can add validateRequest=false to each page, but i'd rather not do
that. Does Microsoft have documentation showing exactly what triggers this
error? I'm unable to find this if so.

Thanks for any suggestions...

Alex

Check the following link:

http://msdn2.microsoft.com/en-us/library/Bb355989.aspx

"Alex" wrote:

> Hello,
>
> In one of our VB.Net 2003 apps, we're receiving the following error:
> A potentially dangerous Request.QueryString value was detected from the
> client (id="RKVW8oNcLoE=").
>
> At first glance I assumed the '=' was the problem, but when we use
> 'id=VQmAq6M5E/I=' in the same URL it works just fine. Any suggestions? I
> know I can add validateRequest=false to each page, but i'd rather not do
> that. Does Microsoft have documentation showing exactly what triggers this
> error? I'm unable to find this if so.
>
> Thanks for any suggestions...
>
> Alex
>
>
>
>
>

That's exactly what I was hunting for... Thanks

Alex


"Kavita" <> wrote in message
news03C7FCC-9789-44AE-9E21-...
> Check the following link:
>
> http://msdn2.microsoft.com/en-us/library/Bb355989.aspx
>
> "Alex" wrote:
>
>> Hello,
>>
>> In one of our VB.Net 2003 apps, we're receiving the following error:
>> A potentially dangerous Request.QueryString value was detected from the
>> client (id="RKVW8oNcLoE=").
>>
>> At first glance I assumed the '=' was the problem, but when we use
>> 'id=VQmAq6M5E/I=' in the same URL it works just fine. Any suggestions?
>> I
>> know I can add validateRequest=false to each page, but i'd rather not do
>> that. Does Microsoft have documentation showing exactly what triggers
>> this
>> error? I'm unable to find this if so.
>>
>> Thanks for any suggestions...
>>
>> Alex
>>
>>
>>
>>
>>