Trapping a ' potentially dangerous Request.QueryString value'

[John Morgan]

I am attempting to use a try/catch block to trap a querystring which
is caught by ValidateRequest="true" in the @page directive

A simple example of the blockthat does not work is

Try
routeID = Request.QueryString("routeID")
Catch
response.Write("a dangerous query string has been entered")
End Try

when I enter an invalid query string I get an error message in
the browser window as follows:

"A potentially dangerous Request.QueryString value was detected from
the client (routeID="<script>alert('boo')..."). "

However nothing is caught by the Try /Catch block and the page does
not get rendered at all ( buffer currently set to false)

My ultimate objectiveI is to trap this error so that I can redirect to
another page.

Any help on how I can trap this invalid querystring would be
appreciated,

Best wishes,
John Morgan

[Oleg Ogurok]

Put your try/catch block into the appropriate method inside Global.asax

-Oleg.
"John Morgan" <jf*@XXwoodlander.co.uk> wrote in message
news:rq********************************@4ax.com...

I am attempting to use a try/catch block to trap a querystring which
is caught by ValidateRequest="true" in the @page directive

A simple example of the blockthat does not work is

Try
routeID = Request.QueryString("routeID")
Catch
response.Write("a dangerous query string has been entered")
End Try

when I enter an invalid query string I get an error message in
the browser window as follows:

"A potentially dangerous Request.QueryString value was detected from
the client (routeID="<script>alert('boo')..."). "

However nothing is caught by the Try /Catch block and the page does
not get rendered at all ( buffer currently set to false)

My ultimate objectiveI is to trap this error so that I can redirect to
another page.

Any help on how I can trap this invalid querystring would be
appreciated,

Best wishes,
John Morgan