6 Answers, 1 is accepted
I am still having trouble for this even just simply copy code from your site.
with UI version is
<%@ Register Assembly="Telerik.Web.UI, Version=2014.1.403.40, Culture=neutral, PublicKeyToken=121fae78165ba3d4"
Namespace="Telerik.Web.UI" TagPrefix="telerik" %>
<telerik:RadScriptManager runat="server" ID="RadScriptManager1" />
<telerik:RadAsyncUpload runat="server" ID="RadAsyncUpload1" MultipleFileSelection="Automatic" EnableInlineProgress="false" />
<telerik:RadProgressManager runat="server" ID="RadProgressManager1" />
<telerik:RadProgressArea runat="server" ID="RadProgressArea1" />
I have performed some local tests, using the specified version of our controls that you are using - 2014.1.403.40 under the 47.0.2526.73m version of Chrome browser, but I am afraid that I was unable to replicate the problem. Below is a video, demonstrating the behavior at my end:
In addition, in the attachment you can find a simple website that was used for the testing purposes. Could you please give it a try at your end and let us know if the issue still persist. If not, please let us know how it differs from your implementation.
Also, could you test the behavior with our online demos and verify if the problem still persist:
thanks for your testing. it is working fine for local testing environment and even if you access it on server.
but if using client computer to access it in intranet, it will be issue if without login in again.
after i google, I found these links and got an ideas that is chrome breake authentication. so I go IIS server to change Authentication Providers. only keep NTLM. then it is working fine.
Thank you very much for sharing your solution with the community. I hope that this suggestion would help other users, which also encountered this problem with the new release of Chrome. It would be nice if they could also share if it was helpful in theirs scenarios.
Thank you again!
Still having the exact issue with chrome Version 47.0.2526.106 m. It works if you force the windows authentication providers to NTLM. I however cannot due to the nature of the site services. IE, Firefox, and safari all work.
I am afraid that the problem is caused by the new release of the Chrome browser and the above suggestion is a temporal solution. Hopefully, the problematic behavior will be fixed in the upcoming version of the browser.