You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: knowledge-base/asyncupload-red-dot-shown-file-not-uploaded-troubleshooting.md
+25-20Lines changed: 25 additions & 20 deletions
Original file line number
Diff line number
Diff line change
@@ -18,43 +18,48 @@ I am experiencing an issue where a red dot is shown next to every file I attempt
18
18
19
19
# Solution
20
20
To resolve this issue, follow these steps:
21
-
1. Check if you have write permission to your temporary folder. If you are hosting your application in IIS, make sure you have assigned additional permissions to the temporary folder. By default, the temporary upload folder is located at `~/App_Data/RadUploadTemp`. Ensure that the folder has full read and write permissions.
22
-
2. Verify that the `Telerik.Web.UI.WebResource.axd` handler is registered in the `web.config` file. Open the `web.config` file and add the following code snippet within the `<system.web>` section:
21
+
- Check if you have write permission to your temporary folder. If you are hosting your application in IIS, make sure you have assigned additional permissions to the temporary folder. By default, the temporary upload folder is located at `~/App_Data/RadUploadTemp`. Ensure that the folder has full read and write permissions.
22
+
- Verify that the `Telerik.Web.UI.WebResource.axd` handler is registered in the `web.config` file. Open the `web.config` file and add the following code snippet within the `<system.web>` section:
4. You can test if the `Telerik.Web.UI.WebResource.axd` handler is registered correctly by opening the following URL: `https://domain/Telerik.web.ui.webresource.axd?type=rau`. If the output is `{"message" : "RadAsyncUpload handler is registered successfully, however, it may not be accessed directly."}`, then your handler is registered correctly.
43
+
>Note: Test if the `Telerik.Web.UI.WebResource.axd` handler is registered correctly by opening the following URL: `https://[your domain or IP name]/Telerik.web.ui.webresource.axd?type=rau`. If the output is `{"message" : "RadAsyncUpload handler is registered successfully, however, it may not be accessed directly."}`, then your handler is registered correctly.
40
44
41
45
If the issue persists, consider the following additional tips:
42
46
- The file upload will fail if the TemporaryUpload folder is not given enough permissions, even if the permissions of the TargetFolder are set properly. The default temporary upload folder is placed inside the App_data folder, so you have to give full read and write permissions to it as well: ~/App_Data/RadUploadTemp
43
47
- Set the `UseApplicationPoolImpersonation` property as explained in the [Application Pool Impersonation](https://docs.telerik.com/devtools/aspnet-ajax/controls/asyncupload/troubleshooting/common-issues#application-pool-impersonation) article.
44
48
- Exclude the handler from Windows Authentication (NTLM) and Forms Authentication by adding the following code snippet within the `<location path="Telerik.Web.UI.WebResource.axd">` section in the web.config:
45
49
46
50
```xml
47
-
<locationpath="Telerik.Web.UI.WebResource.axd">
48
-
<system.web>
49
-
<authorization>
50
-
<allowusers="?" />
51
-
</authorization>
52
-
</system.web>
53
-
</location>
51
+
<locationpath="Telerik.Web.UI.WebResource.axd">
52
+
<system.web>
53
+
<authorization>
54
+
<allowusers="?" />
55
+
</authorization>
56
+
</system.web>
57
+
</location>
54
58
```
55
59
56
-
- Check if your application is using a valid SSL certificate, as RadAsyncUpload requires it.
57
-
- Review the network requests in the browser dev toolbar or with a tool like Fiddler: https://www.telerik.com/blogs/improve-your-debugging-skills-with-chrome-devtools#inspect-network-requests. It is possible that some other network condition is breaking the requests (for example, a proxy changes or caches the requests while it should not). See what happens with the requests and whether the responses carry useful information (e.g., routing or authentication blocking the request).
60
+
- Check if your application uses a valid SSL certificate, as RadAsyncUpload requires it.
61
+
- The red dot may be due to a large file upload. Configure the control and your app as explained at https://docs.telerik.com/devtools/aspnet-ajax/controls/asyncupload/functionality/uploading-large-files.
62
+
- Review the network requests in the [Chrome DevTools](https://www.telerik.com/blogs/improve-your-debugging-skills-with-chrome-devtools#inspect-network-requests) or with a tool like Fiddler: https://www.telerik.com/blogs/improve-your-debugging-skills-with-chrome-devtools#inspect-network-requests. It is possible that some other network condition is breaking the requests (for example, a proxy changes or caches the requests while it should not). See what happens with the requests and whether the responses carry useful information (e.g., routing or authentication blocking the request).
58
63
- If your application is hosted in a web farm or web garden, follow the guidance provided in the [Web Farm and Load Balancing](https://docs.telerik.com/devtools/aspnet-ajax/controls/asyncupload/troubleshooting/web-farm) article.
59
64
- For Azure WAF Firewall related issues, configure the Azure Application Gateway web application firewall (WAF) to allow the `WebResource.axd` and `Telerik.Web.UI.WebResource.axd` extensions. Refer to the following articles for more information:
60
65
-[Customize web application firewall rules through the Azure portal](https://learn.microsoft.com/en-us/azure/web-application-firewall/ag/application-gateway-customize-waf-rules-portal)
0 commit comments