We noticed that the SharePoint 2010 menus were not working with our Cisco ASA’s WebVPN. If the top level menu had children, they would not show on hover. Then we started noticing that all jQuery based functions stopped working. It seemed that much of the Javascript used with SharePoint 2010 would not work with our ASA. The fix was to add this to the web.config for the SharePoint site:
<system.web.extensions> <scripting> <scriptResourceHandler enableCompression="false" enableCaching="true" /> </scripting> </system.web.extensions>
Obviously you are adding the scriptResourceHandler to an exiting scripting section and not replacing what is already there.
That you very much for this post. This resolved an issue we have been struggling with for quite some time between SharePoint and our ASA.
Glad I could help!
This works great for me too. I’m curious why Cisco does not have this documented anywhere. Sharepoint 2010 should be fully supported.
Can you explain what enableCompression=”false” enableCaching=”true” actually does? Other than knowing it works, I would like to know if it might cause other problems in the future. Thanks.
Honestly, I don’t know but I have not seen any issues. WebVPN functionality was a very important requirement, so we had to do it.
Sorry.
No, problem. I appreciate the help. Just curious, how did you find out about it?
Support call!
Dumb question – which web.config file do we need to put this in?
I put it in the one for the site:
C:\inetpub\wwwroot\wss\VirtualDirectories\site.name.com.com80\web.config
We had this problem too. The SharePoint ribbon was stuck on ‘Loading’ and would never appear. Also other functions like “Create New Site” didn’t work.
After adding these lines in the web.config files for our two web applications (portal and mysites) it started working immediately.
Thank you very much for sharing this information!
Thanks so much JBMurphy!! Was lost and having issues with outside vendors being able to upload documents using ribbon. Ribbon was staying stuck at loading, added this script to webconfig and things are working fine now for users!
Can you tell me where you added the script to the web.config file please? I added it to the very end of the file, and it broke it alltogether.