Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
A potentially dangerous Request.Path
Message
De
01/09/2011 11:44:04
 
 
À
01/09/2011 11:15:16
Information générale
Forum:
ASP.NET
Catégorie:
Autre
Versions des environnements
Environment:
VB 9.0
OS:
Windows 7
Network:
Windows 2003 Server
Database:
MS SQL Server
Application:
Web
Divers
Thread ID:
01522446
Message ID:
01522485
Vues:
20
>>Sorry, I should have looked more closely at your code.
>>You can't use it in that way. As per the link RequestValidationType Property is simply defined as an attribute of HttpRuntimeSection:
>>http://msdn.microsoft.com/en-us/library/system.web.configuration.httpruntimesection.requestvalidationtype.aspx
>>You need a class such as this:
Public Class MyRequestValidator
>>	Inherits System.Web.Util.RequestValidator
>>	Protected Overrides Function IsValidRequestString(context As HttpContext, value As String, requestValidationSource__1 As System.Web.Util.RequestValidationSource, collectionKey As String, ByRef validationFailureIndex As Integer) As Boolean
>>		validationFailureIndex = 0
>>
>>		'Spurious rejection test
>>		If requestValidationSource__1 = RequestValidationSource.RawUrl AndAlso value.Contains("Default") Then
>>			Return False
>>		End If
>>
>>
>>		Return MyBase.IsValidRequestString(context, value, requestValidationSource__1, collectionKey, validationFailureIndex)
>>	End Function
>>End Class
and then reference that in web.config.....
>
>Thanks, so basically, the class was good but a reference was still needed in Web.Config.

Yep. Remember that you can use different versions of web.config at different levels in a web site hierarchy which would allow you to fine tune by using different rules for different areas if required
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform