I got a temporary solution by adding a custom HTTP header in IIS : Cache-Control no-cache
But still problem is there when working with Cassini web server while developing using VS 2005
Hi Ajith,
????I tested your Ajax enabled website in Visual Studio .NET 2005 with Ajax RC 1.0 in IE 7.0 and found it worked fine.So I suggest you to upgrade to IE 7.0 and it should work fine.Maybe this problem is caused by the IE 6.0 SP2.
Thanks Jasson,
But since we are developing web sites to support different browsers, upgrading the browser seems to be a temporary solution. When some one with IE 6 SP2 access the site they will not be able to run our site due to JavaScript errors
If the javascript error is caused by IE 6.0 with SP2,I can not give you further help.We need to request this issue to IE Dev Team.
Hi,
I got the same error. I have Windows 2000 SP4 and IE 6 SP1.
I clear IE cache and when I try to load a page of the AjaxControlToolkit (and on my own web site), it works on the first page but it does not work anymore then (after postback or going to another page).
So I try to use configuration of ScriptResourceHandler in web.config and I notice that when I disable compression (and caching in the same time) with :
<system.web.extensions>
<scripting>
<scriptResourceHandler enableCompression="false" enableCaching="false" />
</scripting>
</system.web.extensions>
Then it works just fine, it is a work around, but it is a pity if it is impossible to use this fonctionnality that increases performance.
I noticed also that when I change enableCaching value, it does not change anything to the Expires header, it is always one year more the date the resource was requested. I will write a post on this bug.
Can you give me your opinion and test these problems.
Thanks
Clément
It seems that the caching issue solved in the ASP.NET AJAX 1.0 release. Now there is no script error in IE 6 SP2!!
Thanks
Madfun
Thank you very much for this result.
I was working on a webapplication using AJAX.net and VS2008, but when we checked the browser compatibility with firefox and IE6 ...
Thanks
No comments:
Post a Comment