solarwinds  |  thwack
in
Search 44,782 posts and 623 resources contributed by 21,553 members or post a topic.

Already Joined? Sign in
[bug?] System.Web.HttpRequestValidationException on adding a filter on High Errors/Discards resource

rated by 0 users
Answered (Verified) This post has 2 verified answers | 1 Reply | 0 Followers


102 Posts
Points 247
jp posted on 09-24-2007 11:47 AM
rated by 0 users

 

Hello.

I was trying to add my own filters to a resource on Orion, and I see that this error included below occurs on every filter attempt.  I thought it was my own syntax until I tried the sample filters provided.  The resource in question is High errors and discards todayOrion Website Error

An error has occurred with the Orion website.

Additional Information

System.Web.HttpRequestValidationException: A potentially dangerous Request.Form value was detected from the client (SubTitle="... XX Today 
 (3548 ERRORS ...").
   at System.Web.HttpRequest.ValidateString(String s, String valueName, String collectionName)
   at System.Web.HttpRequest.ValidateNameValueCollection(NameValueCollection nvc, String collectionName)
   at System.Web.HttpRequest.get_Form()
   at System.Web.HttpRequest.get_HasForm()
   at System.Web.UI.Page.GetCollectionBasedOnMethod(Boolean dontReturnNull)
   at System.Web.UI.Page.DeterminePostBackMode()
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
   at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
   at System.Web.UI.Page.ProcessRequest()
   at System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context)
   at System.Web.UI.Page.ProcessRequest(HttpContext context)
   at ASP.orion_proxy_aspx.ProcessRequest(HttpContext context)
   at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
   at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

A few example filters are :

Filter the results to only show Nodes that are not UP
Status<>1

The valid status levels are :

0 = UNKNOWN (The current up/down status of the Node is unknown)
1 = UP (The Node is responding to PINGs)
2 = DOWN (The Node is not responding)
3 = WARNING (The Node may be responding, but the connection from the server to the Node is dropping packets)

Only show Cisco devices
Vendor = 'Cisco'

Only show devices in Atlanta. (This assumes you have added a custom property named City)
City = 'Atlanta'

Only show devices beginning with "AX3-"
Caption Like 'AX3-*'

Only show Nortel devices that are Down
Vendor Like 'Nortel*' AND Status=2

Only show devices ending in '-TX'
Vendor Like '*-TX'

 

My opinions are of my own, and not those of my employers

Answered (Verified) Verified Answers


102 Posts
Points 247
Answered (Verified) jp Posted: 09-24-2007 11:47 AM
rated by 0 users

 

Hello.

I was trying to add my own filters to a resource on Orion, and I see that this error included below occurs on every filter attempt.  I thought it was my own syntax until I tried the sample filters provided.  The resource in question is High errors and discards todayOrion Website Error

An error has occurred with the Orion website.

Additional Information

System.Web.HttpRequestValidationException: A potentially dangerous Request.Form value was detected from the client (SubTitle="... XX Today 
 (3548 ERRORS ...").
   at System.Web.HttpRequest.ValidateString(String s, String valueName, String collectionName)
   at System.Web.HttpRequest.ValidateNameValueCollection(NameValueCollection nvc, String collectionName)
   at System.Web.HttpRequest.get_Form()
   at System.Web.HttpRequest.get_HasForm()
   at System.Web.UI.Page.GetCollectionBasedOnMethod(Boolean dontReturnNull)
   at System.Web.UI.Page.DeterminePostBackMode()
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
   at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
   at System.Web.UI.Page.ProcessRequest()
   at System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context)
   at System.Web.UI.Page.ProcessRequest(HttpContext context)
   at ASP.orion_proxy_aspx.ProcessRequest(HttpContext context)
   at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
   at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

A few example filters are :

Filter the results to only show Nodes that are not UP
Status<>1

The valid status levels are :

0 = UNKNOWN (The current up/down status of the Node is unknown)
1 = UP (The Node is responding to PINGs)
2 = DOWN (The Node is not responding)
3 = WARNING (The Node may be responding, but the connection from the server to the Node is dropping packets)

Only show Cisco devices
Vendor = 'Cisco'

Only show devices in Atlanta. (This assumes you have added a custom property named City)
City = 'Atlanta'

Only show devices beginning with "AX3-"
Caption Like 'AX3-*'

Only show Nortel devices that are Down
Vendor Like 'Nortel*' AND Status=2

Only show devices ending in '-TX'
Vendor Like '*-TX'

 

My opinions are of my own, and not those of my employers


102 Posts
Points 247
Answered (Verified) jp replied on 09-24-2007 1:10 PM
rated by 0 users

-I was using "Interface Errors <br /> Except 3548s -jp" as the description for the resource.

I don't think it liked one of the html markup characters or the hyphen -.

 Resolved.

My opinions are of my own, and not those of my employers

  • | Post Points: 1

All Replies


102 Posts
Points 247
Answered (Verified) jp replied on 09-24-2007 1:10 PM
rated by 0 users

-I was using "Interface Errors <br /> Except 3548s -jp" as the description for the resource.

I don't think it liked one of the html markup characters or the hyphen -.

 Resolved.

My opinions are of my own, and not those of my employers

  • | Post Points: 1
Page 1 of 1 (2 items) | RSS