Hi
I have the RadEditor implemented, everything works, image uploads, deletes, image map, image editor, etc. However when I right click the image in the content and choose properties I get a Forbidden 403 error. Image Map Editor does however work!
Any ideas?
I have the RadEditor implemented, everything works, image uploads, deletes, image map, image editor, etc. However when I right click the image in the content and choose properties I get a Forbidden 403 error. Image Map Editor does however work!
Any ideas?
You don't have permission to access http://website/admin/content/Telerik.Web.UI.DialogHandler.aspx?DialogName=ImageProperties&UseRSM=true&Skin=Default&Title=Properties...&doid=0a82807c-b422-4396-8fe0-3a4124eab91e&dpptn=&dp=XXX on this server.
4 Answers, 1 is accepted
0
Hi Michael,
The problem could be due to some antivirus, firewall, proxy or websense tool that is blocking the URL of the Image Properties dialog. The RadEditor dialogs receive encoded arguments such as skin and configuration information (for example the ImagesPaths, DialogCssFiles) via the URL. In addition RadEditor follows the HTTP rules, which allow up to 2000 symbols to be used for the URL length. However, if some monitoring program such as WebSense or a Proxy server decrease the URL length for example to 1700 symbols then this could break the loading of the editor dialogs and cause the reported error. The solution is to contact your network administrator and increase the allowed URL length to 2000 symbols.
You can find other reasons for the error in this article: HTTP Error 403 Forbidden.
You can also inspect with Fiddler what is returned by the server when loading the Properties dialog as well as check the server event logs. If possible, please, provide a live URL to the problematic page so that we can test it.
Best wishes,
Rumen
the Telerik team
The problem could be due to some antivirus, firewall, proxy or websense tool that is blocking the URL of the Image Properties dialog. The RadEditor dialogs receive encoded arguments such as skin and configuration information (for example the ImagesPaths, DialogCssFiles) via the URL. In addition RadEditor follows the HTTP rules, which allow up to 2000 symbols to be used for the URL length. However, if some monitoring program such as WebSense or a Proxy server decrease the URL length for example to 1700 symbols then this could break the loading of the editor dialogs and cause the reported error. The solution is to contact your network administrator and increase the allowed URL length to 2000 symbols.
You can find other reasons for the error in this article: HTTP Error 403 Forbidden.
You can also inspect with Fiddler what is returned by the server when loading the Properties dialog as well as check the server event logs. If possible, please, provide a live URL to the problematic page so that we can test it.
Best wishes,
Rumen
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Public Issue Tracking
system and vote to affect the priority of the items
0

Michael
Top achievements
Rank 1
answered on 05 Nov 2010, 01:31 AM
Thanks, I found what the problem is. We use HeliconTech ISAPI Rewrite 3 which is causing this issue under Windows 7 however it seems to work ok on the production server which runs Windows 2003.
0
Hello Michael,
Thank you for this information. I will use it if anyone else report this problem. Your points were updated as well.
Best regards,
Rumen
the Telerik team
Thank you for this information. I will use it if anyone else report this problem. Your points were updated as well.
Best regards,
Rumen
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Public Issue Tracking
system and vote to affect the priority of the items
0

Michael
Top achievements
Rank 1
answered on 10 Dec 2010, 01:08 AM
Ok more debugging I have tracked the exact HeliconTech ISAPI_Rewrite rule that spat out this error.
# Defend from worm attacks
RewriteRule .*(?:global\.asa|root\.exe|\.\.).* . [F,I,O]
So if that rule is not present then RadEditor will work as desired with ISAPI_Rewrite installed.
# Defend from worm attacks
RewriteRule .*(?:global\.asa|root\.exe|\.\.).* . [F,I,O]
So if that rule is not present then RadEditor will work as desired with ISAPI_Rewrite installed.