3 Answers, 1 is accepted
0
Vazqusa
Top achievements
Rank 1
Rank 1
answered on 27 Aug 2013, 02:09 PM
Any update on this, @telerik team ?
0
Hello Vazqusa,
The experienced behavior is not caused by an Editor's (or FileExplorer's) limitation, but indicates that the publishing was cancelled due to the ASP.NET validators detecting a dangerous input in the request path. This information concerns the following characters: <,>,*,%,&,:,\. You could predefine the set of the restricted characters by both setting ValidateRequest="false" to the page, containing the Editor and adding the following property in the <httpRuntime> section of the web.config:
More detailed information on the subject could be found here: HttpRuntimeSection.RequestPathInvalidCharacters Property
There is another set of characters, which are told to be unsaved or/and reserved ones. You can find detailed information about them here and here.
There is also a third set of characters, which are restricted by the operating system itself - http://screencast.com/t/AxABxovEk7
In short, event if you configure your application to skip the path validation, there will remain symbols, which could not be used as a path to a file. I hope the following video will shed some light on the subject: video.
You can also look at the following KB article, if you decide to restrict the using of such characters at all: How to notify the user that an image with invalid file name is being uploaded.
Additionally, please note, that our support system assigns a response time for all questions, depending on the client's license. You can find detailed information regarding the different support plans and how to activate them here: Support Plans
Regards,
Veselina Raykova
Telerik
The experienced behavior is not caused by an Editor's (or FileExplorer's) limitation, but indicates that the publishing was cancelled due to the ASP.NET validators detecting a dangerous input in the request path. This information concerns the following characters: <,>,*,%,&,:,\. You could predefine the set of the restricted characters by both setting ValidateRequest="false" to the page, containing the Editor and adding the following property in the <httpRuntime> section of the web.config:
<system.web> <httpRuntime enableVersionHeader="false" maxUrlLength="1200" maxRequestLength="1572864000" executionTimeout="18000" relaxedUrlToFileSystemMapping="true" requestPathInvalidCharacters="" /></system.web>More detailed information on the subject could be found here: HttpRuntimeSection.RequestPathInvalidCharacters Property
There is another set of characters, which are told to be unsaved or/and reserved ones. You can find detailed information about them here and here.
There is also a third set of characters, which are restricted by the operating system itself - http://screencast.com/t/AxABxovEk7
In short, event if you configure your application to skip the path validation, there will remain symbols, which could not be used as a path to a file. I hope the following video will shed some light on the subject: video.
You can also look at the following KB article, if you decide to restrict the using of such characters at all: How to notify the user that an image with invalid file name is being uploaded.
Additionally, please note, that our support system assigns a response time for all questions, depending on the client's license. You can find detailed information regarding the different support plans and how to activate them here: Support Plans
Regards,
Veselina Raykova
Telerik
If you want to get updates on new releases, tips and tricks and sneak peeks at our product labs directly from the developers working on the RadControls for ASP.NET AJAX, subscribe to the blog feed now.
0
Vazqusa
Top achievements
Rank 1
Rank 1
answered on 29 Aug 2013, 03:12 PM
thanks, had already implemented the same, but thank any way.