I understand I can use validateRequest="false" to by pass ASP.NET security. I'd like to know what security issues setting this flag may cause. Can I be 100% sure there won't be any issue as long as I encode the input using a XSS library?
View 3 Repliestell me the use of Validaterequest False?
View 4 RepliesI'm using FreeTextBox HTML editor in some webforms in my asp.net project . if I do not set ValidateRequest property to false I get this error :
A potentially dangerous Request.Form value was detected from the client
It's OK in admin folder though , Because only authorized users have access to work with it . But how about public pages like sections where every users have access to leave comments(using FreeTextBox for collecting users comment ) ? Isn't risky for XSS Attack ? If the answer is not Yes , So what's ValidateRequest property for?
FYI I am using .NET 4.0 / MVC 3. In my controller, the following is my code:
[HttpPost]
[ValidateInput(false)]
public ViewResult Edit(ContentTemplateView contentTemplateView, FormCollection collection)
Everything works fine when I don't enter HTML, so I know the proper controller is being fired. Also, I have following set properly in my web.config files:
<httpRuntime requestValidationMode="2.0"/>
I only get this problem when I include the FormCollection (which is needed for this particular Controller). So what exactly am I doing wrong? [I have done what was proposed on the following questions, and they work as long as there is no FormCollection. None of them offer a solution with an included FormCollection] Why is ValidateInput(False) not working? Asp.Net MVC Input Validation still firing after being disabled ValidateInput Attribute Doesn't Seem To Work in ASP.NET MVC
Is it possible to send a html text entered in asp.net text box without making validaterequest to false.
View 1 RepliesI have a textbox and i want the user to be able to submit a youtube embed code.
Is this possible without setting 'ValidateRequest' to false?
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 have an app that was originally running fine in ASP.Net 3.5, using the ValidateRequest set to false to allow HTML to be saved from a rich text box. However, after converting the app to 4.0, I am getting the Potentially Dangerous message, even though both the page and web.config have the value set to false.
I went into the page and created a PagesSection object and checked its value and then set the value to false. Everytime the page is hit (postback or new) the value is always returned as true, until I set it to false. Not sure why it is reverting to true.
When I set fckEditor to Some Value like
fckDescription.Value = "Description Text";
It creates problems such as Update Panel not doing Async PostBack for DropDownList control and gives error when DropDownList selection changes:Sys.WebForms.PageRequestManagerServerErrorException: An unknown error occurred while processing the request on the server. The status code returned from the server was: 500
But when I Comment out these lines
// fckDescription.Value = "Description Text";
It Works Fine... I am wondering why it is so !!?!!
Also, fckEditor is outside UpdatePanel and DropDownList Control is inside UpdatePanel.
Do sites like Stackoverflow or asp.net use validateRequest= "false" at their page directive? If "Yes" then how they are checking the user input and if "NO" then how they are able to postback the data ?
View 1 RepliesI use fckedit 2.6.6 control in asp.net 4.0 (FCKeditor_2.6.6 and FCKeditor.Net_2.6.3)
somebody told me I should add ValidateRequest="false" to aspx,
but my aspx works well without add ValidateRequest="false",
I'm wanting to allow users to enter HTML in only a single textbox. I understand it's possible to change ValidateRequest in the Page directive to false in order to remove protection.I'm guessing that this allows HTML to be entered in any textbox on the page. Is there anyway to apply ValidateRequest=False on only a single control?
View 3 Replies(ASP.NET 4.0 C#)
I have my <httpRuntime requestValidationMode="2.0" /> in the webconfig. AndI have my validateRequest="false" in page directories.On one page, I send some data (html) from a ckeditor (textarea) to a database. Works fine.On another page I fill the ckeditor with data from a database, then I update it (send it back), and I get the famous "A potentially dangerous Request.Form value was detected from the client."
Makes me very confused. The only difference is that on the second page the data gets dynamically inserted into the textarea, where on the first page the textarea is empty on pageload. Am i missing something here? Im pretty sure Encoding/decoding doesnt mean anything, as the framework stops it before I can even start messing with it on the backend.
I have a form at which I use ckeditor. This form worked fine but now doesn't work in Asp.Net 4. I have ValidateRequest="false" directive.
View 3 RepliesHere's the situation. I have an aspx page that is designed to receive a POST request with some XML values, parse the XML, grab the relevant items, and write them to the page. The problem arises when I try to launch the page using the POST request. When I launch using Fiddler, building the request manually and just pasting the XML in the body of the request everything works fine and dandy. When I launch the page from a basic HTML form, however, things don't go so great. The HTML form that I'm using looks like this:
[Code]....
When the page loads I get the error:
A potentially dangerous Request.Form value was detected from the client Everything I've read so far has told me that the solution is to add ValidateRequest="false" to the page directive in the top of the .aspx file, or in the pages element of the web.config file. But neither of these work. Afterwards, I still get the same error. Any idea what I need to do to make this work?
I've noticed that setting ValidateRequest="true" on the page blocks input of the form • but not • - which are the same characters. Does anyone know why the first type is not allowed but the second type is?I really could not find a place where it defines what is meant by dangerous script and what is actually blocked when the ValidateRequest is set to true.
View 3 Replieswhy the ValidateRequest dose not work when html tags had sent by __doPostBack method in javascript.
<script>
[Code]....
</script>
Do i have to validate cokkies, userinput, qurystring,database out for xxs , when my page is set to
ValidateRequest="true" ??
I intend to use SSL on the login form so that the username and password is encrypted during user login. But, after the user has been authenticated, if I return to HTTP, the Autentication Cookie will be passed from client to server on each request. How safe is this? Obviously i'll use SSL on pages where the user is entering sensitive information, but for most of the time, for performance reasons, i'll just want them to remain authenticated and use HTTP.
I note that if I set RequiresSSL="True" in my forms authentication section in web.config then the authentication cookie is not passed if I use HTTP so I cannot identify the current user. "Is it bad practice to set RequiresSSL="false" and allow the Authentication cookie to pass over HTTP"?
I'm working with the default asp.net membershipprovider. Now, by default, that requires that all members registere have all unique email-addresses.However, I'd like to override that because, in a code behind of a certain webpage, I do not need emails to be unique.
View 4 RepliesWhen a user creates an account can not sign until his account is manually approved.I use the Membership. The table column IsApproved.When I create account must be IsApproved = False
View 3 RepliesI have configured Forms Authentication in my web config file as below.
Following is my code
[Code]....
The issue is that FormsAuthentication.Authenticate never returns true. This is a very simple website with only two pages and no other code(The code too was copied from MSDN).
[Code]....
i trying to include a name property which is save in aspnet_Profile when registering user with aspnet_Membership
I try to assign a name to the newly registered user but at first it pop outa ProviderException saying "This property cannot be set for anonymous users."
Then i try to set the IsAnonymous to False in the code, but it say the property is ReadOnly
How do i fix this problem? Or is there any better way to do this?
Below is my code.
[Code]....
Our web application hosted from windows 2003 server, is trying to access a file present in a shared folder of another windows 2003 server. The path for the shared folder is configured in the webconfig file in the below format.
<add key="ReportPath" value="\<Server_Name>Reports"/>
if (!File.Exists(ReportPath))
/ Show the report in a link
This function File.Exists() always returns false and when I try to remove the check, it returned the exception, "Logon failure: unknown username or bad password."
I have a webpage stored on a local server (Site A) which when I browse to it is given my windows account details, this site then checks within AD to get my email address. My email address is then passed to another website (Site B) and consumed. The Website A is set in IIS to Integrated Windows Auth Only, WebSite A has
<identity impersonate="false"/>
set in the web.config What I dont understand is what user is accessing AD from site A - with impersonate = false that is telling the site not impersonate the windows user, but this seems at odds with the setting in IIS.