my issue seemed to have gone away when I added CDATA tags. but now it is back after I updated the site and I dont know why. I am also using JQuery in my page....if that matters...
Sorry for cross-posting, but this thread seems a bit more active than the one at
Microsoft Feedback .
We are still trying to figure this one out... we've seen an increase of Invalid Viewstate-errors in our logs and every single one is IE8. The increase is due to the fact that the Windows Update is rolling out IE8. Approximately 20% of our customers now have
IE8 and almost exactly 10% of the IE8s get this error.
We get the exception for both ScriptResource.axd and WebResource.axd.
Our theory is that it has something to do with slower clients, low bandwidth and possibly with firewall/antivirus application (in combianation with IE8).
I've managed to get the exception twice just by clicking furiously at our ajax-components (before they are finished loading). But, I have no fail-safe way to get it. I took me like 500 tests to get 2 exceptions [:)]
shahed.kazi
All-Star
17953 Points
3635 Posts
Re: Corrupted WebResource.axd url parameters
May 28, 2009 08:18 AM|LINK
You should not worry about the parameters in the webresource.axd file. Changing the urls will cause problems in your site.
.NET World |Captcha Control
Deathknight
Member
14 Points
7 Posts
Re: Corrupted WebResource.axd url parameters
Jun 03, 2009 01:27 PM|LINK
Again with this guy? You need to worry about the URLs when they are CORRUPTED!
Deathknight
Member
14 Points
7 Posts
Re: Corrupted WebResource.axd url parameters
Jun 04, 2009 04:18 PM|LINK
I have just confirmed that when we experience this error, exactly 4k is missing from the body of the page as well.
JoeVolcano
Member
26 Points
13 Posts
Re: Corrupted WebResource.axd url parameters
Jun 04, 2009 05:38 PM|LINK
my issue seemed to have gone away when I added CDATA tags. but now it is back after I updated the site and I dont know why. I am also using JQuery in my page....if that matters...
shahed.kazi
All-Star
17953 Points
3635 Posts
Re: Corrupted WebResource.axd url parameters
Jun 05, 2009 09:38 AM|LINK
you should not modify the wemresource file parameters. That's automatically generated based on your code.
.NET World |Captcha Control
JoeVolcano
Member
26 Points
13 Posts
Re: Corrupted WebResource.axd url parameters
Jun 05, 2009 01:20 PM|LINK
Read the thread. no one is talking about modifiying the parameters.
duran_dal
Member
4 Points
2 Posts
Re: Corrupted WebResource.axd url parameters
Jun 05, 2009 06:03 PM|LINK
Sorry for cross-posting, but this thread seems a bit more active than the one at Microsoft Feedback .
We are still trying to figure this one out... we've seen an increase of Invalid Viewstate-errors in our logs and every single one is IE8. The increase is due to the fact that the Windows Update is rolling out IE8. Approximately 20% of our customers now have IE8 and almost exactly 10% of the IE8s get this error.
We get the exception for both ScriptResource.axd and WebResource.axd.
Our theory is that it has something to do with slower clients, low bandwidth and possibly with firewall/antivirus application (in combianation with IE8).
I've managed to get the exception twice just by clicking furiously at our ajax-components (before they are finished loading). But, I have no fail-safe way to get it. I took me like 500 tests to get 2 exceptions [:)]
JoeVolcano
Member
26 Points
13 Posts
Re: Corrupted WebResource.axd url parameters
Jun 06, 2009 08:42 PM|LINK
Has anyone opened a ticket with microsoft? Has anyone been able to fix this issue?
duran_dal
Member
4 Points
2 Posts
Re: Corrupted WebResource.axd url parameters
Jun 08, 2009 01:00 PM|LINK
It seems even more likely that this is a bug in IE8. See this post.
Deathknight
Member
14 Points
7 Posts
Re: Corrupted WebResource.axd url parameters
Jun 09, 2009 05:09 PM|LINK