I have one asp.net application, which has some problems while i am entering the special characters such as ": &#, " in the search box. If i enter this text in search box, i got the exception like this. A potentially dangerous Request.Form value was detected from the client (txtValue=": &#, ").
then i searched on the net, i got one general solution for this that to set the validaterequest to false. But no changes has been made on my application.
When Iuse FTB in a normal web form I am having no issues. However when I create a master page then a web form that uses that master page I get the following error when pulling text from the FTB control
A potentially dangerous Request.Form value was detected from the client (ctl00_ContentPlaceHolder1_FreeTextBox1="<b>My TEXT</b>")
I get this error only when it uses html tags and only when its in a form that uses a master page.
I am writing a database to store code extracts which will make our life easier at work, I have a text box which retrieves HTML characters, I have no problems in displaying them, however if I click the edit button to amend text I get the error "A potentially danger Request.Form value was detected from the client (txtCodeExtract=" etc").
I have added ValidateRequest="False" to the main form however, when I now click the edit button the textbox wipes out all the text.
I have tried using the Server.HTMLEncode(txtCodeExtracts.Text); or Decode and HttpUtility.HTMLEncode or Decode but the textbox still clears. This is a web app using Visual Studio 2008
[Update : I have inserted this post in "XML Web Services" section by mistake, so if you are a moderator or Admin, please shift it to "Security" section or any other relevant section]
I am working with WCF REST Service Application in .Net 4.0 and my service is hosted on II7 (Windows 7 Ultimate - 64 bit).My service and all other code is working completely fine.But when I use the '&' character in request url, it shows the following Error.I have already tried adding following section in my web.config as shown here on www.asp.net
On a windows 2008 web server, I get the following error whenever posting a form containing html tags in textboxes:
A potentially dangerous Request.Form value was detected from the client (widget$txtText="
This is a common error and you fix it by either doing Page ValidateRequest = false or in the web.config with pages validaterequest = false. However, on this specific server, it completely ignores the validaterequest = false and throws this exception anyway. Has anyone seen this behavior before and know what else I can do to prevent this error? I've seen it in 2 web apps now on the same server, it's really weird.
I am using Webhandler to upload images to the server. I want to send the folder name so on that folder the images will save. I am using this URI format and got the below error.
Also I added the following line in the web.config but still having the issue.
<httpRuntime requestValidationMode="2.0" />
A potentially dangerous Request.Path value was detected from the client (?). Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Web.HttpException: A potentially dangerous Request.Path value was detected from the client (?).
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace: [HttpException (0x80004005): A potentially dangerous Request.Path value was detected from the client (?).] System.Web.HttpRequest.ValidateInputIfRequiredByConfig() +8884233 System.Web.ValidateRequestExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +35 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +184
Version
Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.1
and also i set the ValidateRequest="false" in the page directive's. and in code behind i also use HttpUtility.HtmlEncode . but again and again i am facing this error
"A potentially dangerous Request.Form value was detected from the client (ctl00$ContentPlaceHolder1$txtEmbed="<embed src='http://a...").".
I have a form that a user fills out and can input html or other text into a textarea. I have the validaterequest attribute set to false on the page. However, when I submit the form with any html characters it bombs saying that it detected the potentially dangerous request field and to make validaterequest=false. I've already done this so I'm not sure why it's not working. I've done this many times before and never had this problem. Anyone run into this before and if so, is there a fix? I don't want to update my web.config and apply it site wide.
I'm trying to create roles for my web application using the Role class methods provided in ASP.net but when I attempt to use the class methods as such:
I have an ashx handler that was working fine in VS2008 but when I upgraded to VS2010 (haven't gone back to VS2008 to double check though) and when I try to grab the value from HttpContext.Request.Params["update"] I get the following error:
+ ex {"A potentially dangerous Request.QueryString value was detected from the client (update="<SETIProducts><Produ...")."} System.Exception {System.Web.HttpRequestValidationException}
I'm using a php script to http post some xml files to a .net URL.
When I submit I get the response:
A potentially dangerous Request.Form value was detected from the client (<?xml version="...UTF-8"?> <!DOCTYPE cXML SYSTE...").
Description: Request Validation has detected a potentially dangerous client input value, and processing of the request has been aborted. This value may indicate an attempt to compromise the security of your application, such as a cross-site scripting attack. You can disable request validation by setting validateRequest=false in the Page directive or in the configuration section. However, it is strongly recommended that your application explicitly check all inputs in this case.
As I'm not using .NET I can't set ValidateRequest="false" in web.config.
Do I need to sanitize my xml before submitiing? How can I do this?
I know the < and > characters will cause this error, but what other characters/inputs will cause this error?
I'm testing for this error in the Global.asax, and reridrecting to an error page where I want to list all possible values which cause this error, so the user can go back to their page and get rid of them.
I've done some googling, but all I see so far are the < and > characters...surely there are more out there.
To prevent my application from crashing with the error "A potentially dangerous Request.Form value was detected...", I just turned page validation off. I want to revisit this and solve it correctly. Is there a good strategy for this? If people are entering '<' and '>', I think the only way to save their data is to encode it via Javacript. I have tried catching it in the code-behind, but it becomes too late. I am thinking of inheriting the textbox and auto encode/decode the input with client scripts. I also have to think of all the angle brackets that are already saved in my database.
i have created loing form and create user form. then how to apply login rights..? i have 2 types of user. admin and normal user admin can move and use all pages while normal user can acces limited pages.
I want to show the admin pages only after logging in a form with username and password and also want to logout from the admin pages, if in the browser history select a admin page after logout it should not be shown
In this asp.net web application, users can upload files to the server through a web interface. All the uploaded files are save in a server side folder. If I want to create a new win form desktop client (actually, its a WPF application) which can be used to upload files to that same server side folder as web interface does, how can I share that server side folder with that win form client?
I am fresh new to asp.net. I try to convert my windows form into asp.net application. On my Windows form I use threads to monitor for changes in data sources to udpate my controls.However, I got no clue how to accomplish this in asp.net form. It seems I cannot create a thread in the page to update my controls in the page.
I'm trying to get most of the data I have on my web page, to update a query during an asp 2.0 raisecallback event. I've tried Request.Form with no luck. I've got the html (sent in raisecallback parameter) using 2 div tag's innerhtml. Can someone tell me an efficient method to use to get all this data for updating - Do I have to parse from the callback string (eventArgument) & if so can I use a reader of somekind, or is there a better way?
Is there any way to add a confirmation dialog to a submit button when the form already has other validation controls and a summary control using "showmessagebox=true"? I tried adding
OnClientClick="return confirm('Are you sure?');" to the submit button, but that seems to block all of the other validation?
When I click submit, It does the validation on the server side, I kinda like it to validate on the Client instead of taking a trip to the server right away.
I've set up a system with forms based authentication and using the asp:Login control. When I put in an invalid password I get the approriate invalid password message. However when I put in a valid password, it does nothing...just returns to the login page again. I'm triple checked the login info. There is no error message, and the invalid attempts counter doesn't increment. When I put a break point in the Login_LoggedIn event of the Login form, it hits it, but User.Identity.IsAuthenticated is false. I'm not 100% sure it should be true at this point, as I'm pretty new to .NET but it seems kind of odd.
My user database is stored in a sqlserver 2005 db that already existed. I've added a new connection for it.In the authorization I have
Am running asp.net application.Am searching records.if i click the view button i got this error,
an inconsistency was detected during an internal operation in database(database name) on page(some page).please contact technical support.reference number 6.
I Googled and i got the result as to run DBCC CHECKDB. I run the following command in sql server 2005,
DBCC CHECKDB (database name) WITH NO_INFOMSGS, ALL_ERRORMSGS
my result was something like this
Table error: Object ID 1424372489, index ID 1, partition ID 374822652149760, alloc unit ID 93347675439104 (type In-row data). Page (1:72872) is missing a reference from previous page (1:72871). Possible chain linkage problem.
Msg 8928, Level 16, State 1, Line 1 Object ID 1424372489, index ID 1, partition ID 374822652149760, alloc unit ID 93347675439104 (type In-row data): Page (1:109577) could not be processed. See other errors for details. Msg 8978, Level 16, State 1, Line 1 Table error: Object ID 1424372489, index ID 1, partition ID 374822652149760, alloc unit ID 93347675439104 (type In-row data). Page (1:109578) is missing a reference from previous page (1:109577). Possible chain linkage problem. Msg 8976, Level 16, State 1, Line 1
CHECKDB found 0 allocation errors and 10 consistency errors in table 'some table' (object ID 1424372489). CHECKDB found 0 allocation errors and 5 consistency errors in table 'some table' (object ID 1432300808). CHECKDB found 0 allocation errors and 19 consistency errors in database 'database name'. repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (database name).